Skip to content

Commit

Permalink
New translations ql-schema.mdx (French)
Browse files Browse the repository at this point in the history
  • Loading branch information
benface committed Dec 16, 2024
1 parent a3fb6a6 commit 30db611
Showing 1 changed file with 15 additions and 15 deletions.
30 changes: 15 additions & 15 deletions website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two

Les scalaires suivants sont supportés dans l'API GraphQL :

| Type | Description |
| --- | --- |
| `Bytes` | Tableau d'octets, représenté sous forme de chaîne hexadécimale. Couramment utilisé pour les hachages et adresses Ethereum. |
| `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 be a signed 32-bit integer. |
| `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. |
| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
| Type | Description |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Bytes` | Tableau d'octets, représenté sous forme de chaîne hexadécimale. Couramment utilisé pour les hachages et adresses Ethereum. |
| `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 be a signed 32-bit integer. |
| `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. |
| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |

### Enums

Expand Down Expand Up @@ -210,7 +210,7 @@ Cette approche nécessite que les requêtes descendent vers un niveau supplémen
query usersWithOrganizations {
users {
organizations {
# ceci est une entité UserOrganization
# ceci est une entité UserOrganization
organization {
name
}
Expand Down Expand Up @@ -306,7 +306,7 @@ Dictionnaires de langues pris en charge :

Algorithmes de classement:

| Algorithm | Description |
| --- | --- |
| rank | Utilisez la qualité de correspondance (0-1) de la requête en texte intégral pour trier les résultats. |
| proximitéRang | Similar to rank but also includes the proximity of the matches. |
| Algorithm | Description |
| ------------- | ----------------------------------------------------------------------------------------------------- |
| rank | Utilisez la qualité de correspondance (0-1) de la requête en texte intégral pour trier les résultats. |
| proximitéRang | Similar to rank but also includes the proximity of the matches. |

0 comments on commit 30db611

Please sign in to comment.