From 2fe44ef4f6acc07a184ea3c71ded92f1555fda3d Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 07:59:57 -0500 Subject: [PATCH 01/11] explorer.mdx mistake: 'In the The Curators table' --- website/src/pages/en/subgraphs/explorer.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/explorer.mdx b/website/src/pages/en/subgraphs/explorer.mdx index ddb6ad1b39b6..059016cf1bf2 100644 --- a/website/src/pages/en/subgraphs/explorer.mdx +++ b/website/src/pages/en/subgraphs/explorer.mdx @@ -116,7 +116,7 @@ Curators analyze Subgraphs to identify which Subgraphs are of the highest qualit - By depositing GRT, Curators mint curation shares of a Subgraph. As a result, they can earn a portion of the query fees generated by the Subgraph they have signaled on. - The bonding curve incentivizes Curators to curate the highest quality data sources. -In the The Curator table listed below you can see: +In the Curators table listed below you can see: - The date the Curator started curating - The number of GRT that was deposited From 837877566856a4f06063a784a4c4308808ebdeca Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 08:29:44 -0500 Subject: [PATCH 02/11] best-practices: fixed 'handled by the GraphQL server The GraphQL' --- website/src/pages/en/subgraphs/querying/best-practices.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/best-practices.mdx b/website/src/pages/en/subgraphs/querying/best-practices.mdx index ec7d4070c18d..54524abcaa2d 100644 --- a/website/src/pages/en/subgraphs/querying/best-practices.mdx +++ b/website/src/pages/en/subgraphs/querying/best-practices.mdx @@ -154,7 +154,7 @@ const result = await execute(query, { Static strings have several **key advantages**: - Queries are easier to read, manage, and debug. -- Variable sanitization is handled by the GraphQL server The GraphQL. +- Variable sanitization is handled by the GraphQL server. - Variables can be cached at the server level. - Queries can be statically analyzed by tools (see [GraphQL Essential Tools](/subgraphs/querying/best-practices/#graphql-essential-tools-guides)). From 5820436db694831a3fbe358e6c5a2895227a0848 Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 08:38:00 -0500 Subject: [PATCH 03/11] best-practices: "Dos" is a simple plural (not possessive) - apostrophe removed --- website/src/pages/en/subgraphs/querying/best-practices.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/best-practices.mdx b/website/src/pages/en/subgraphs/querying/best-practices.mdx index 54524abcaa2d..6c1479a6ef30 100644 --- a/website/src/pages/en/subgraphs/querying/best-practices.mdx +++ b/website/src/pages/en/subgraphs/querying/best-practices.mdx @@ -362,7 +362,7 @@ When using the types generation tool, the above query will generate a proper `De ## GraphQL Fragment Guidelines -### Do's and Don'ts for Fragments +### Dos and Don'ts for Fragments 1. Fragments cannot be based on a non-applicable types (types without fields). 2. `BigInt` cannot be used as a fragment's base because it's a **scalar** (native "plain" type). From 2df5c7490bfdd3a9045ae687e98df324f7cfb569 Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 08:40:22 -0500 Subject: [PATCH 04/11] best-practices: removed extra article --- website/src/pages/en/subgraphs/querying/best-practices.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/best-practices.mdx b/website/src/pages/en/subgraphs/querying/best-practices.mdx index 6c1479a6ef30..f10b57eb4624 100644 --- a/website/src/pages/en/subgraphs/querying/best-practices.mdx +++ b/website/src/pages/en/subgraphs/querying/best-practices.mdx @@ -364,7 +364,7 @@ When using the types generation tool, the above query will generate a proper `De ### Dos and Don'ts for Fragments -1. Fragments cannot be based on a non-applicable types (types without fields). +1. Fragments cannot be based on non-applicable types (types without fields). 2. `BigInt` cannot be used as a fragment's base because it's a **scalar** (native "plain" type). Example: From 8c1c241d0da546c75187db786595bed0837f2e32 Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 09:45:37 -0500 Subject: [PATCH 05/11] querying-graph-client: sentence had extra words --- website/src/pages/en/subgraphs/querying/graph-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index 416cadc13c6f..498b483b9379 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -4,7 +4,7 @@ This repo is the home for [The Graph](https://thegraph.com) consumer-side tools ## Background -The tools provided in this repo are intended to enrich and extend the DX, and add the additional layer required for dApps in order to implement distributed applications. +The tools provided in this repo are intended to enrich and extend the DX, and add the additional layer required for dApps to implement distributed applications. Developers who consume data from [The Graph](https://thegraph.com) GraphQL API often need peripherals for making data consumption easier, and also tools that allow using multiple indexers at the same time. From aa1abeef8ae7d7badcd624baae9c72fd1874025a Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 09:50:11 -0500 Subject: [PATCH 06/11] 'tools provided' are plural and then described as singular. It was written more like 'this repo' was the subject. Fixed. --- website/src/pages/en/subgraphs/querying/graph-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index 498b483b9379..fed483545cd1 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -12,7 +12,7 @@ Developers who consume data from [The Graph](https://thegraph.com) GraphQL API o This library is intended to simplify the network aspect of data consumption for dApps. The tools provided within this repository are intended to run at build time, in order to make execution faster and performant at runtime. -> The tools provided in this repo can be used as standalone, but you can also use it with any existing GraphQL Client! +> The tools provided in this repo can be used as standalones, but you can also use them with any existing GraphQL Client! | Status | Feature | Notes | | :----: | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | From d2693477d7fd39afdbf3693d120efd155c5d0c48 Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 09:55:00 -0500 Subject: [PATCH 07/11] querying-graph-client: fixed comma misuse. --- website/src/pages/en/subgraphs/querying/graph-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index fed483545cd1..19b27ac49b88 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -67,7 +67,7 @@ graphclient build > Note: you need to run this with `yarn` prefix, or add that as a script in your `package.json`. -This should produce a ready-to-use standalone `execute` function, that you can use for running your application GraphQL operations, you should have an output similar to the following: +This should produce a ready-to-use standalone `execute` function that you can use for running your application GraphQL operations. You should have an output similar to the following: ```sh GraphClient: Cleaning existing artifacts From 2f29da1997752fd640de8c64e1cede9d92c8a5ba Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 09:57:16 -0500 Subject: [PATCH 08/11] querying-graph-client: cleaned a sentence up to read more efficiently. --- website/src/pages/en/subgraphs/querying/graph-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index 19b27ac49b88..ee0aedaad387 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -80,7 +80,7 @@ GraphClient: Reading the configuration 🕸️: Done! => .graphclient ``` -Now, the `.graphclient` artifact is generated for you, and you can import it directly from your code, and run your queries: +Now that the `.graphclient` artifact is generated for you, you can import it directly from your code, and run your queries: ```ts import { execute } from '../.graphclient' From c1e71db0e6d3668bfb37e72d389fc5d4b3530c46 Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 10:05:26 -0500 Subject: [PATCH 09/11] 'As long as there a no conflicts' changed to 'As long as there are no conflicts' --- website/src/pages/en/subgraphs/querying/graph-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index ee0aedaad387..529814e299f8 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -449,7 +449,7 @@ sources: endpoint: https://api.thegraph.com/subgraphs/name/graphprotocol/compound-v2 ``` -As long as there a no conflicts across the composed schemas, you can compose it, and then run a single query to both Subgraphs: +As long as there are no conflicts across the composed schemas, you can compose it, and then run a single query to both Subgraphs: ```graphql query myQuery { From 48b9158ba8379d5828826c90a241dcc004e73a76 Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 10:09:08 -0500 Subject: [PATCH 10/11] 'has' becomes 'have' because 'client libraries like...' is pluralizing the subject. --- website/src/pages/en/subgraphs/querying/graph-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index 529814e299f8..e72fec1b7240 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -482,7 +482,7 @@ For advanced use-cases with composition, please refer to the following resources If your project is written in TypeScript, you can leverage the power of [`TypedDocumentNode`](https://the-guild.dev/blog/typed-document-node) and have a fully-typed GraphQL client experience. -The standalone mode of The GraphQL, and popular GraphQL client libraries like Apollo-Client and urql has built-in support for `TypedDocumentNode`! +The standalone mode of The GraphQL, and popular GraphQL client libraries like Apollo-Client and urql have built-in support for `TypedDocumentNode`! The Graph Client CLI comes with a ready-to-use configuration for [GraphQL Code Generator](https://graphql-code-generator.com), and it can generate `TypedDocumentNode` based on your GraphQL operations. From 3f91d3169e749c76bec7ee28bb385e8cbf154987 Mon Sep 17 00:00:00 2001 From: nathan-websculpt Date: Wed, 9 Jul 2025 10:12:11 -0500 Subject: [PATCH 11/11] 'a' changed to 'an' --- website/src/pages/en/subgraphs/querying/graph-client/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/subgraphs/querying/graph-client/README.md b/website/src/pages/en/subgraphs/querying/graph-client/README.md index e72fec1b7240..c6dd72b133d7 100644 --- a/website/src/pages/en/subgraphs/querying/graph-client/README.md +++ b/website/src/pages/en/subgraphs/querying/graph-client/README.md @@ -530,7 +530,7 @@ This is helpful since you can implement custom code as part of your GraphQL sche > This document explains how to add custom mutations, but in fact you can add any GraphQL operation (query/mutation/subscriptions). See [Extending the unified schema article](https://graphql-mesh.com/docs/guides/extending-unified-schema) for more information about this feature. -To get started, define a `additionalTypeDefs` section in your config file: +To get started, define an `additionalTypeDefs` section in your config file: ```yaml additionalTypeDefs: |