New translations creating-a-subgraph.mdx (Yoruba)

graphprotocol · Dec 26, 2023 · 8933339 · 8933339
1 parent bc8292e
commit 8933339
Showing 1 changed file with 11 additions and 11 deletions.
diff --git a/website/pages/yo/developing/creating-a-subgraph.mdx b/website/pages/yo/developing/creating-a-subgraph.mdx
@@ -248,15 +248,15 @@ For some entity types the `id` is constructed from the id's of two other entitie
 
 We support the following scalars in our GraphQL API:
 
-| Type | Description |
-| --- | --- |
-| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
-| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
-| `Boolean` | Scalar for `boolean` values. |
-| `Int` | The GraphQL spec defines `Int` to have a size of 32 bytes. |
-| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to have a size of 32 bytes.                                                                                                                                                       |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
 
 #### Enums
 
@@ -659,7 +659,7 @@ export function handleNewExchange(event: NewExchange): void {
 ```
 
 > **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
->
+> 
 > If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
 
 ### Data Source Context
@@ -716,7 +716,7 @@ dataSources:
 ```
 
 > **Note:** The contract creation block can be quickly looked up on Etherscan:
->
+> 
 > 1. Search for the contract by entering its address in the search bar.
 > 2. Click on the creation transaction hash in the `Contract Creator` section.
 > 3. Load the transaction details page where you'll find the start block for that contract.