From 0b0c3a7b2fbb9455795952434a82c0392c18b49c Mon Sep 17 00:00:00 2001 From: Saihajpreet Singh Date: Mon, 1 May 2023 11:56:26 -0400 Subject: [PATCH] fix: point docs to graph tooling for example subgraph --- website/pages/ar/cookbook/arweave.mdx | 2 +- website/pages/ar/cookbook/cosmos.mdx | 10 +++++----- website/pages/ar/cookbook/near.mdx | 4 ++-- website/pages/ar/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/ar/developing/creating-a-subgraph.mdx | 2 +- website/pages/de/cookbook/arweave.mdx | 2 +- website/pages/de/cookbook/cosmos.mdx | 10 +++++----- website/pages/de/cookbook/near.mdx | 4 ++-- website/pages/de/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/de/developing/creating-a-subgraph.mdx | 2 +- website/pages/en/cookbook/arweave.mdx | 2 +- website/pages/en/cookbook/cosmos.mdx | 10 +++++----- website/pages/en/cookbook/near.mdx | 4 ++-- website/pages/en/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/en/developing/creating-a-subgraph.mdx | 2 +- website/pages/es/cookbook/arweave.mdx | 2 +- website/pages/es/cookbook/cosmos.mdx | 10 +++++----- website/pages/es/cookbook/near.mdx | 4 ++-- website/pages/es/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/es/developing/creating-a-subgraph.mdx | 2 +- website/pages/fr/cookbook/arweave.mdx | 2 +- website/pages/fr/cookbook/cosmos.mdx | 10 +++++----- website/pages/fr/cookbook/near.mdx | 4 ++-- website/pages/fr/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/fr/developing/creating-a-subgraph.mdx | 2 +- website/pages/hi/cookbook/arweave.mdx | 2 +- website/pages/hi/cookbook/cosmos.mdx | 10 +++++----- website/pages/hi/cookbook/near.mdx | 4 ++-- website/pages/hi/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/hi/developing/creating-a-subgraph.mdx | 2 +- website/pages/it/cookbook/arweave.mdx | 2 +- website/pages/it/cookbook/cosmos.mdx | 10 +++++----- website/pages/it/cookbook/near.mdx | 4 ++-- website/pages/it/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/it/developing/creating-a-subgraph.mdx | 2 +- website/pages/ja/cookbook/arweave.mdx | 2 +- website/pages/ja/cookbook/cosmos.mdx | 10 +++++----- website/pages/ja/cookbook/near.mdx | 4 ++-- website/pages/ja/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/ja/developing/creating-a-subgraph.mdx | 2 +- website/pages/ko/cookbook/arweave.mdx | 2 +- website/pages/ko/cookbook/cosmos.mdx | 10 +++++----- website/pages/ko/cookbook/near.mdx | 4 ++-- website/pages/ko/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/ko/developing/creating-a-subgraph.mdx | 2 +- website/pages/mr/cookbook/arweave.mdx | 2 +- website/pages/mr/cookbook/cosmos.mdx | 10 +++++----- website/pages/mr/cookbook/near.mdx | 4 ++-- website/pages/mr/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/mr/developing/creating-a-subgraph.mdx | 2 +- website/pages/nl/cookbook/arweave.mdx | 2 +- website/pages/nl/cookbook/cosmos.mdx | 10 +++++----- website/pages/nl/cookbook/near.mdx | 4 ++-- website/pages/nl/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/nl/developing/creating-a-subgraph.mdx | 2 +- website/pages/pl/cookbook/arweave.mdx | 2 +- website/pages/pl/cookbook/cosmos.mdx | 10 +++++----- website/pages/pl/cookbook/near.mdx | 4 ++-- website/pages/pl/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/pl/developing/creating-a-subgraph.mdx | 2 +- website/pages/pt/cookbook/arweave.mdx | 2 +- website/pages/pt/cookbook/cosmos.mdx | 10 +++++----- website/pages/pt/cookbook/near.mdx | 4 ++-- website/pages/pt/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/pt/developing/creating-a-subgraph.mdx | 2 +- website/pages/ru/cookbook/arweave.mdx | 2 +- website/pages/ru/cookbook/cosmos.mdx | 10 +++++----- website/pages/ru/cookbook/near.mdx | 4 ++-- website/pages/ru/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/ru/developing/creating-a-subgraph.mdx | 2 +- website/pages/sv/cookbook/arweave.mdx | 2 +- website/pages/sv/cookbook/cosmos.mdx | 10 +++++----- website/pages/sv/cookbook/near.mdx | 4 ++-- website/pages/sv/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/sv/developing/creating-a-subgraph.mdx | 2 +- website/pages/tr/cookbook/arweave.mdx | 2 +- website/pages/tr/cookbook/cosmos.mdx | 10 +++++----- website/pages/tr/cookbook/near.mdx | 4 ++-- website/pages/tr/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/tr/developing/creating-a-subgraph.mdx | 2 +- website/pages/uk/cookbook/arweave.mdx | 2 +- website/pages/uk/cookbook/cosmos.mdx | 10 +++++----- website/pages/uk/cookbook/near.mdx | 4 ++-- website/pages/uk/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/uk/developing/creating-a-subgraph.mdx | 2 +- website/pages/ur/cookbook/arweave.mdx | 2 +- website/pages/ur/cookbook/cosmos.mdx | 10 +++++----- website/pages/ur/cookbook/near.mdx | 4 ++-- website/pages/ur/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/ur/developing/creating-a-subgraph.mdx | 2 +- website/pages/vi/cookbook/arweave.mdx | 2 +- website/pages/vi/cookbook/cosmos.mdx | 10 +++++----- website/pages/vi/cookbook/near.mdx | 4 ++-- website/pages/vi/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/vi/developing/creating-a-subgraph.mdx | 2 +- website/pages/zh/cookbook/arweave.mdx | 2 +- website/pages/zh/cookbook/cosmos.mdx | 10 +++++----- website/pages/zh/cookbook/near.mdx | 4 ++-- website/pages/zh/cookbook/subgraph-debug-forking.mdx | 2 +- website/pages/zh/developing/creating-a-subgraph.mdx | 2 +- 100 files changed, 200 insertions(+), 200 deletions(-) diff --git a/website/pages/ar/cookbook/arweave.mdx b/website/pages/ar/cookbook/arweave.mdx index 621077fd974a..d8876009af1c 100644 --- a/website/pages/ar/cookbook/arweave.mdx +++ b/website/pages/ar/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## الأسئلة الشائعة diff --git a/website/pages/ar/cookbook/cosmos.mdx b/website/pages/ar/cookbook/cosmos.mdx index a8aae5522179..bbd67fcff9c6 100644 --- a/website/pages/ar/cookbook/cosmos.mdx +++ b/website/pages/ar/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. فيما يلي بعض الأمثلة على الـ subgraphs للرجوع إليها: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/ar/cookbook/near.mdx b/website/pages/ar/cookbook/near.mdx index 1821abfeab87..e312f2ae9ce4 100644 --- a/website/pages/ar/cookbook/near.mdx +++ b/website/pages/ar/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, فيما يلي بعض الأمثلة على الـ subgraphs للرجوع إليها: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## الأسئلة الشائعة diff --git a/website/pages/ar/cookbook/subgraph-debug-forking.mdx b/website/pages/ar/cookbook/subgraph-debug-forking.mdx index d4f49169a530..0d331deab109 100644 --- a/website/pages/ar/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/ar/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ title: Quick and Easy Subgraph Debugging Using Forks ## من فضلك ، أرني بعض الأكواد! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. فيما يلي المعالجات المعرفة لفهرسة `Gravatar` ، بدون أخطاء على الإطلاق: diff --git a/website/pages/ar/developing/creating-a-subgraph.mdx b/website/pages/ar/developing/creating-a-subgraph.mdx index 36182c1508d7..ffd8fedebdd9 100644 --- a/website/pages/ar/developing/creating-a-subgraph.mdx +++ b/website/pages/ar/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ Subgraph manifest `subgraph.yaml` تحدد العقود الذكية لفهار ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/de/cookbook/arweave.mdx b/website/pages/de/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/de/cookbook/arweave.mdx +++ b/website/pages/de/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/de/cookbook/cosmos.mdx b/website/pages/de/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/de/cookbook/cosmos.mdx +++ b/website/pages/de/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/de/cookbook/near.mdx b/website/pages/de/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/de/cookbook/near.mdx +++ b/website/pages/de/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/de/cookbook/subgraph-debug-forking.mdx b/website/pages/de/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/de/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/de/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/de/developing/creating-a-subgraph.mdx b/website/pages/de/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/de/developing/creating-a-subgraph.mdx +++ b/website/pages/de/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/en/cookbook/arweave.mdx b/website/pages/en/cookbook/arweave.mdx index 55f820e120d0..ae61228949b4 100644 --- a/website/pages/en/cookbook/arweave.mdx +++ b/website/pages/en/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/en/cookbook/cosmos.mdx b/website/pages/en/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/en/cookbook/cosmos.mdx +++ b/website/pages/en/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/en/cookbook/near.mdx b/website/pages/en/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/en/cookbook/near.mdx +++ b/website/pages/en/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/en/cookbook/subgraph-debug-forking.mdx b/website/pages/en/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/en/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/en/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/en/developing/creating-a-subgraph.mdx b/website/pages/en/developing/creating-a-subgraph.mdx index 683b7dbaa086..ccbf7d724411 100644 --- a/website/pages/en/developing/creating-a-subgraph.mdx +++ b/website/pages/en/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/es/cookbook/arweave.mdx b/website/pages/es/cookbook/arweave.mdx index d91be92da856..b2e398ec8e9b 100644 --- a/website/pages/es/cookbook/arweave.mdx +++ b/website/pages/es/cookbook/arweave.mdx @@ -166,7 +166,7 @@ El endpoint de GraphQL para los subgrafos de Arweave está determinado por la de A continuación se muestra un ejemplo de subgrafo como referencia: -- [Ejemplo de subgrafo para Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Ejemplo de subgrafo para Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## Preguntas frecuentes diff --git a/website/pages/es/cookbook/cosmos.mdx b/website/pages/es/cookbook/cosmos.mdx index 49debaec9cb7..1013116b6abb 100644 --- a/website/pages/es/cookbook/cosmos.mdx +++ b/website/pages/es/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ Puedes encontrar una lista completa de los tipos para la integración Cosmos aqu Es importante tener en cuenta que los mensajes de Cosmos son específicos de la cadena y se pasan a un subgrafo en forma de una carga de Protocol Buffers serializada [Protocol Buffers](https://developers.google.com/protocol-buffers/) Como resultado, los datos del mensaje deben decodificarse en una función de mapeo antes de que puedan ser procesados. Un ejemplo de cómo decodificar los datos de un mensaje en un subgrafo se puede encontrar aquí. -Un ejemplo de cómo decodificar los datos de un mensaje en un subgrafo se puede encontrar aquí [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +Un ejemplo de cómo decodificar los datos de un mensaje en un subgrafo se puede encontrar aquí [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Crear y construir un subgrafo de Cosmos @@ -250,10 +250,10 @@ La red principal de Osmosis es `osmosis-1`. La red de prueba actual de Osmosis e A continuación se presentan algunos ejemplos de subgrafos como referencia: -[Ejemplo de filtrado de bloques](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Ejemplo de filtrado de bloques](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Ejemplo de recompensas del validador](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Ejemplo de recompensas del validador](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Ejemplo de delegaciones de validador](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Ejemplo de delegaciones de validador](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Ejemplo de intercambio de tokens de Osmosis](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Ejemplo de intercambio de tokens de Osmosis](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/es/cookbook/near.mdx b/website/pages/es/cookbook/near.mdx index 363d37ae8529..c5c079141781 100644 --- a/website/pages/es/cookbook/near.mdx +++ b/website/pages/es/cookbook/near.mdx @@ -235,9 +235,9 @@ El endpoint de GraphQL para los subgrafos NEAR está determinado por la definici A continuación se presentan algunos ejemplos de subgrafos como referencia: -[Bloques NEAR](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[Bloques NEAR](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[Recibos NEAR](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[Recibos NEAR](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## Preguntas frecuentes diff --git a/website/pages/es/cookbook/subgraph-debug-forking.mdx b/website/pages/es/cookbook/subgraph-debug-forking.mdx index 08177fcca5ac..1e2d42925fad 100644 --- a/website/pages/es/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/es/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ En pocas palabras, vamos a _bifurcar el subgrafo fallido_ desde un nodo de Graph ## ¡Por favor, muéstrame algo de código! -Para mantenernos enfocados en el debugging de subgrafos, simplifiquemos las cosas y sigamos con el [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) que indexa el contrato inteligente Ethereum Gravity. +Para mantenernos enfocados en el debugging de subgrafos, simplifiquemos las cosas y sigamos con el [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) que indexa el contrato inteligente Ethereum Gravity. Estos son los handlers definidos para indexar `Gravatar`s, sin errores de ningún tipo: diff --git a/website/pages/es/developing/creating-a-subgraph.mdx b/website/pages/es/developing/creating-a-subgraph.mdx index 82f4b4d2c821..bb846ec17d6e 100644 --- a/website/pages/es/developing/creating-a-subgraph.mdx +++ b/website/pages/es/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ Para este subgrafo de ejemplo, `subgraph.yaml` es: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/fr/cookbook/arweave.mdx b/website/pages/fr/cookbook/arweave.mdx index c6c83b281322..cde716f93d53 100644 --- a/website/pages/fr/cookbook/arweave.mdx +++ b/website/pages/fr/cookbook/arweave.mdx @@ -166,7 +166,7 @@ Le endpoint GraphQL pour les subgraphes d'Arweave est déterminé par la défini Voici un exemple de modèle subgraphe : -- [Exemple de subgraphe pour Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Exemple de subgraphe pour Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/fr/cookbook/cosmos.mdx b/website/pages/fr/cookbook/cosmos.mdx index 62a844df631d..3b784e9fd10c 100644 --- a/website/pages/fr/cookbook/cosmos.mdx +++ b/website/pages/fr/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ Vous pouvez trouver la liste complète des types pour l'intégration Cosmos [ici Il est important de noter que les messages Cosmos sont spécifiques à une chaîne et qu'ils sont transmis à un sous-graphe sous la forme d'une charge utile sérialisée [Protocol Buffers](https://developers.google.com/protocol-buffers/). Par conséquent, les données du message doivent être décodées dans une fonction de mappage avant de pouvoir être traitées. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Création et construction d'un subgraphe Cosmos @@ -250,10 +250,10 @@ Le réseau principal d'Osmosis est `osmosis-1`. Le réseau de test actuel d'Osmo Voici quelques exemples de subgraphes pour référence : -[Exemple de filtrage par blocs](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Exemple de filtrage par blocs](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Exemple de récompenses de validateurs](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Exemple de récompenses de validateurs](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Exemple de délégation de validateurs](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Exemple de délégation de validateurs](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Exemple d'échange de jetons Osmosis](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Exemple d'échange de jetons Osmosis](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/fr/cookbook/near.mdx b/website/pages/fr/cookbook/near.mdx index c03c1ee32ab7..5c57a62fbcef 100644 --- a/website/pages/fr/cookbook/near.mdx +++ b/website/pages/fr/cookbook/near.mdx @@ -235,9 +235,9 @@ Le point de terminaison GraphQL pour les subgraphes NEAR est déterminé par la Voici quelques exemples de subgraphes pour référence : -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/fr/cookbook/subgraph-debug-forking.mdx b/website/pages/fr/cookbook/subgraph-debug-forking.mdx index 824f5a630f85..4b394e33e000 100644 --- a/website/pages/fr/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/fr/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ En bref, nous allons _fork le subgraphe défaillant_ à partir d'un nœud The Gr ## Je vous en prie, montrez-moi du code ! -Pour rester concentré sur le débogage des subgraphes, gardons les choses simples et suivons l'[exemple du subgraphe](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexant le contrat intelligent Ethereum Gravity. +Pour rester concentré sur le débogage des subgraphes, gardons les choses simples et suivons l'[exemple du subgraphe](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexant le contrat intelligent Ethereum Gravity. Voici les gestionnaires définis pour l'indexation des `Gravatars`, sans le moindre bug : diff --git a/website/pages/fr/developing/creating-a-subgraph.mdx b/website/pages/fr/developing/creating-a-subgraph.mdx index 750c7001d62d..64171c133f27 100644 --- a/website/pages/fr/developing/creating-a-subgraph.mdx +++ b/website/pages/fr/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/hi/cookbook/arweave.mdx b/website/pages/hi/cookbook/arweave.mdx index ff9992342dba..7bba73f38de2 100644 --- a/website/pages/hi/cookbook/arweave.mdx +++ b/website/pages/hi/cookbook/arweave.mdx @@ -166,7 +166,7 @@ graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph सहायता के एक सब-ग्राफ का उदाहरण -- [आरवीव के लिए उदाहरण सब-ग्राफ](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [आरवीव के लिए उदाहरण सब-ग्राफ](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## सामान्य प्रश्न diff --git a/website/pages/hi/cookbook/cosmos.mdx b/website/pages/hi/cookbook/cosmos.mdx index a5872c660f26..6985b03cecc3 100644 --- a/website/pages/hi/cookbook/cosmos.mdx +++ b/website/pages/hi/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ class Any { यह गौर करना अत्यंत जरुरी है कि कॉसमॉस के मैसेज चेन-विशिष्ट हैं और उन्हें सब-ग्राफ्स में एक क्रमबद्ध [प्रोटोकॉल बफर्स](https://developers.google.com/protocol-buffers/) की तरह पास किया जाता है| परिणामस्वरूप, मैसेज के डाटा को प्रोसेस करने से पहले मैपिंग फंक्शन में डिकोड करने की आवश्यकता होती है| -सब-ग्राफ में मैसेज डिकोड करने का एक उदहारण [यहाँ](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts) से देखें| +सब-ग्राफ में मैसेज डिकोड करने का एक उदहारण [यहाँ](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts) से देखें| ## कॉसमॉस सब-ग्राफ्स बनाना और निर्माण करना @@ -250,10 +250,10 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost सन्दर्भ के लिए कुछ सब-ग्राफ्स के उदाहरण: -[ब्लॉक फ़िल्टर उदहारण](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[ब्लॉक फ़िल्टर उदहारण](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[सत्यापनकर्ता इनाम उदाहरण](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[सत्यापनकर्ता इनाम उदाहरण](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[सत्यापनकर्ता प्रतिनिधि मंडल उदाहरण](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[सत्यापनकर्ता प्रतिनिधि मंडल उदाहरण](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[ऑस्मोसिस टोकन अदला-बदली उदाहरण](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[ऑस्मोसिस टोकन अदला-बदली उदाहरण](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/hi/cookbook/near.mdx b/website/pages/hi/cookbook/near.mdx index 6651dadba0e6..f6439ed027cf 100644 --- a/website/pages/hi/cookbook/near.mdx +++ b/website/pages/hi/cookbook/near.mdx @@ -235,9 +235,9 @@ NEAR सबग्राफ के लिए ग्राफक्यूएल संदर्भ के लिए यहां कुछ उदाहरण सबग्राफ दिए गए हैं: -[NEAR ब्लॉक्स](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR ब्लॉक्स](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR रेसिप्टस](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR रेसिप्टस](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## सामान्य प्रश्न diff --git a/website/pages/hi/cookbook/subgraph-debug-forking.mdx b/website/pages/hi/cookbook/subgraph-debug-forking.mdx index e21dd55ae61e..835c1b217cc0 100644 --- a/website/pages/hi/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/hi/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ title: फोर्क्स का उपयोग करके त्वरि ## कृपया मुझे कुछ कोड दिखाओ! -सबग्राफ डिबगिंग पर ध्यान केंद्रित करने के लिए, चीजों को सरल रखें और [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) एथेरियम ग्रेविटी स्मार्ट कॉन्ट्रैक्ट को इंडेक्स करने के साथ चलें। +सबग्राफ डिबगिंग पर ध्यान केंद्रित करने के लिए, चीजों को सरल रखें और [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) एथेरियम ग्रेविटी स्मार्ट कॉन्ट्रैक्ट को इंडेक्स करने के साथ चलें। `Gravatar`s को अनुक्रमणित करने के लिए परिभाषित हैंडलर यहां दिए गए हैं, बिना किसी बग के: diff --git a/website/pages/hi/developing/creating-a-subgraph.mdx b/website/pages/hi/developing/creating-a-subgraph.mdx index 70e76edd1ae6..516ce70185a5 100644 --- a/website/pages/hi/developing/creating-a-subgraph.mdx +++ b/website/pages/hi/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ Options: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/it/cookbook/arweave.mdx b/website/pages/it/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/it/cookbook/arweave.mdx +++ b/website/pages/it/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/it/cookbook/cosmos.mdx b/website/pages/it/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/it/cookbook/cosmos.mdx +++ b/website/pages/it/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/it/cookbook/near.mdx b/website/pages/it/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/it/cookbook/near.mdx +++ b/website/pages/it/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/it/cookbook/subgraph-debug-forking.mdx b/website/pages/it/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/it/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/it/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/it/developing/creating-a-subgraph.mdx b/website/pages/it/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/it/developing/creating-a-subgraph.mdx +++ b/website/pages/it/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/ja/cookbook/arweave.mdx b/website/pages/ja/cookbook/arweave.mdx index e4f05080f35f..abdc7a52c841 100644 --- a/website/pages/ja/cookbook/arweave.mdx +++ b/website/pages/ja/cookbook/arweave.mdx @@ -166,7 +166,7 @@ Arweave サブグラフの GraphQL エンドポイントは、スキーマ定義 参考までにサブグラフの例を紹介します: -- [Arweave のサブグラフの例](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Arweave のサブグラフの例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## よくある質問 diff --git a/website/pages/ja/cookbook/cosmos.mdx b/website/pages/ja/cookbook/cosmos.mdx index e4fd59d50dca..f87c7fc4ec83 100644 --- a/website/pages/ja/cookbook/cosmos.mdx +++ b/website/pages/ja/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ Cosmos 統合の全種類一覧は[こちら](https://github.com/graphprotocol/g Cosmos のメッセージはチェーンに固有であり、シリアル化された[Protocol Buffers](https://developers.google.com/protocol-buffers/)ペイロードの形でサブグラフに渡されることに注意することが重要です。その結果、メッセージデータは処理される前にマッピング関数でデコードされる必要があります。 -サブグラフのメッセージデータをデコードする例は、[こちら](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts)で見ることができます。 +サブグラフのメッセージデータをデコードする例は、[こちら](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts)で見ることができます。 ## Cosmos サブグラフの作成と構築 @@ -250,10 +250,10 @@ Osmosis メインネットは`osmosis-1`です。現在のテストネットは 参考までにサブグラフの例を紹介します: -[ブロックフィルタリング例](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[ブロックフィルタリング例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[バリデータ報酬の例](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[バリデータ報酬の例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[バリデータ・デリゲーションの例](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[バリデータ・デリゲーションの例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis トークンスワップの例](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis トークンスワップの例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/ja/cookbook/near.mdx b/website/pages/ja/cookbook/near.mdx index 8c9628e07804..e02d2c3fb709 100644 --- a/website/pages/ja/cookbook/near.mdx +++ b/website/pages/ja/cookbook/near.mdx @@ -235,9 +235,9 @@ NEAR サブグラフの GraphQL エンドポイントは、既存の API イン 参考までにサブグラフの例を紹介します: -[NEAR ブロック](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR ブロック](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR 領収書](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR 領収書](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## よくある質問 diff --git a/website/pages/ja/cookbook/subgraph-debug-forking.mdx b/website/pages/ja/cookbook/subgraph-debug-forking.mdx index 7d22ee73175b..302c920016cd 100644 --- a/website/pages/ja/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/ja/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ title: フォークを用いた迅速かつ容易なサブグラフのデバッ ## コードを見てみましょう -サブグラフのデバッグに集中するために、物事をシンプルにして、Ethereum Gravity スマートコントラクトのサブグラフのインデックス作成の[例](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar)に沿って実行しましょう。 +サブグラフのデバッグに集中するために、物事をシンプルにして、Ethereum Gravity スマートコントラクトのサブグラフのインデックス作成の[例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar)に沿って実行しましょう。 以下は、`Gravatar`のインデックスを作成するために定義されたハンドラで、バグが全くありません。 diff --git a/website/pages/ja/developing/creating-a-subgraph.mdx b/website/pages/ja/developing/creating-a-subgraph.mdx index 652e5b26627e..8c70fd0c96a8 100644 --- a/website/pages/ja/developing/creating-a-subgraph.mdx +++ b/website/pages/ja/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ Options: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/ko/cookbook/arweave.mdx b/website/pages/ko/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/ko/cookbook/arweave.mdx +++ b/website/pages/ko/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/ko/cookbook/cosmos.mdx b/website/pages/ko/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/ko/cookbook/cosmos.mdx +++ b/website/pages/ko/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/ko/cookbook/near.mdx b/website/pages/ko/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/ko/cookbook/near.mdx +++ b/website/pages/ko/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/ko/cookbook/subgraph-debug-forking.mdx b/website/pages/ko/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/ko/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/ko/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/ko/developing/creating-a-subgraph.mdx b/website/pages/ko/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/ko/developing/creating-a-subgraph.mdx +++ b/website/pages/ko/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/mr/cookbook/arweave.mdx b/website/pages/mr/cookbook/arweave.mdx index 052b741747d6..dbdfb367fda4 100644 --- a/website/pages/mr/cookbook/arweave.mdx +++ b/website/pages/mr/cookbook/arweave.mdx @@ -166,7 +166,7 @@ Arweave subgraphs साठी GraphQL एंडपॉइंट विद्य Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/mr/cookbook/cosmos.mdx b/website/pages/mr/cookbook/cosmos.mdx index c681104820ac..ac17d1db173a 100644 --- a/website/pages/mr/cookbook/cosmos.mdx +++ b/website/pages/mr/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi हे लक्षात घेणे महत्त्वाचे आहे की कॉसमॉस संदेश साखळी-विशिष्ट असतात आणि ते अनुक्रमित [प्रोटोकॉल बफर्स](https://developers.google.com/protocol-buffers/) च्या स्वरूपात सबग्राफवर पाठवले जातात पेलोड. परिणामी, संदेश डेटावर प्रक्रिया करण्यापूर्वी मॅपिंग फंक्शनमध्ये डीकोड करणे आवश्यक आहे. -सबग्राफमध्ये संदेश डेटा कसा डीकोड करायचा याचे उदाहरण [ आढळू शकते. येथे](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +सबग्राफमध्ये संदेश डेटा कसा डीकोड करायचा याचे उदाहरण [ आढळू शकते. येथे](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/mr/cookbook/near.mdx b/website/pages/mr/cookbook/near.mdx index 302d625990ee..9f06b6cb2054 100644 --- a/website/pages/mr/cookbook/near.mdx +++ b/website/pages/mr/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/mr/cookbook/subgraph-debug-forking.mdx b/website/pages/mr/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/mr/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/mr/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/mr/developing/creating-a-subgraph.mdx b/website/pages/mr/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/mr/developing/creating-a-subgraph.mdx +++ b/website/pages/mr/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/nl/cookbook/arweave.mdx b/website/pages/nl/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/nl/cookbook/arweave.mdx +++ b/website/pages/nl/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/nl/cookbook/cosmos.mdx b/website/pages/nl/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/nl/cookbook/cosmos.mdx +++ b/website/pages/nl/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/nl/cookbook/near.mdx b/website/pages/nl/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/nl/cookbook/near.mdx +++ b/website/pages/nl/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/nl/cookbook/subgraph-debug-forking.mdx b/website/pages/nl/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/nl/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/nl/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/nl/developing/creating-a-subgraph.mdx b/website/pages/nl/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/nl/developing/creating-a-subgraph.mdx +++ b/website/pages/nl/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/pl/cookbook/arweave.mdx b/website/pages/pl/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/pl/cookbook/arweave.mdx +++ b/website/pages/pl/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/pl/cookbook/cosmos.mdx b/website/pages/pl/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/pl/cookbook/cosmos.mdx +++ b/website/pages/pl/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/pl/cookbook/near.mdx b/website/pages/pl/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/pl/cookbook/near.mdx +++ b/website/pages/pl/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/pl/cookbook/subgraph-debug-forking.mdx b/website/pages/pl/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/pl/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/pl/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/pl/developing/creating-a-subgraph.mdx b/website/pages/pl/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/pl/developing/creating-a-subgraph.mdx +++ b/website/pages/pl/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/pt/cookbook/arweave.mdx b/website/pages/pt/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/pt/cookbook/arweave.mdx +++ b/website/pages/pt/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/pt/cookbook/cosmos.mdx b/website/pages/pt/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/pt/cookbook/cosmos.mdx +++ b/website/pages/pt/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/pt/cookbook/near.mdx b/website/pages/pt/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/pt/cookbook/near.mdx +++ b/website/pages/pt/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/pt/cookbook/subgraph-debug-forking.mdx b/website/pages/pt/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/pt/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/pt/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/pt/developing/creating-a-subgraph.mdx b/website/pages/pt/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/pt/developing/creating-a-subgraph.mdx +++ b/website/pages/pt/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/ru/cookbook/arweave.mdx b/website/pages/ru/cookbook/arweave.mdx index 6a176511b0ba..9a2e939b200f 100644 --- a/website/pages/ru/cookbook/arweave.mdx +++ b/website/pages/ru/cookbook/arweave.mdx @@ -166,7 +166,7 @@ graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph Вот пример подграфа для справки: -- [Пример подграфа для Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Пример подграфа для Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## Часто задаваемые вопросы diff --git a/website/pages/ru/cookbook/cosmos.mdx b/website/pages/ru/cookbook/cosmos.mdx index 87eb8bb10f82..e526a25e1a73 100644 --- a/website/pages/ru/cookbook/cosmos.mdx +++ b/website/pages/ru/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ class Any { Важно отметить, что сообщения Cosmos зависят от специфики чейна и передаются в субграф в виде серийной полезной нагрузки [Protocol Buffers](https://developers.google.com/protocol-buffers/). В результате данные сообщения необходимо декодировать в функции отображения, прежде чем их можно будет обработать. -Пример того, как расшифровываются данные сообщения в субграфе, можно найти [здесь](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +Пример того, как расшифровываются данные сообщения в субграфе, можно найти [здесь](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Создание и построение субграфа на Cosmos @@ -250,10 +250,10 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost Вот несколько примеров субграфов для справки: -[Пример фильтрации блоков](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Пример фильтрации блоков](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Пример вознаграждения валидатора](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Пример вознаграждения валидатора](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Пример делегирования валидатора](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Пример делегирования валидатора](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Пример свопа токенов Osmosis](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Пример свопа токенов Osmosis](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/ru/cookbook/near.mdx b/website/pages/ru/cookbook/near.mdx index 4374feaf4ffd..77c1750f7373 100644 --- a/website/pages/ru/cookbook/near.mdx +++ b/website/pages/ru/cookbook/near.mdx @@ -235,9 +235,9 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 Вот несколько примеров подграфов для справки: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## Часто задаваемые вопросы diff --git a/website/pages/ru/cookbook/subgraph-debug-forking.mdx b/website/pages/ru/cookbook/subgraph-debug-forking.mdx index 6a01a9acf8fc..d1a5d5b6b5e3 100644 --- a/website/pages/ru/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/ru/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ title: Быстрая и простая отладка подграфа с ис ## Пожалуйста, покажите мне какой-нибудь код! -Чтобы оставаться сосредоточенным на отладке подграфа, давайте сделаем все просто и запустим вместе с [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) индексирование смарт-контракта Ethereum Gravity. +Чтобы оставаться сосредоточенным на отладке подграфа, давайте сделаем все просто и запустим вместе с [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) индексирование смарт-контракта Ethereum Gravity. Вот обработчики, установленные для индексирования `Gravatar`s, совершенно без ошибок: diff --git a/website/pages/ru/developing/creating-a-subgraph.mdx b/website/pages/ru/developing/creating-a-subgraph.mdx index 7ecce778b167..031d4754e1d1 100644 --- a/website/pages/ru/developing/creating-a-subgraph.mdx +++ b/website/pages/ru/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/sv/cookbook/arweave.mdx b/website/pages/sv/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/sv/cookbook/arweave.mdx +++ b/website/pages/sv/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/sv/cookbook/cosmos.mdx b/website/pages/sv/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/sv/cookbook/cosmos.mdx +++ b/website/pages/sv/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/sv/cookbook/near.mdx b/website/pages/sv/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/sv/cookbook/near.mdx +++ b/website/pages/sv/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/sv/cookbook/subgraph-debug-forking.mdx b/website/pages/sv/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/sv/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/sv/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/sv/developing/creating-a-subgraph.mdx b/website/pages/sv/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/sv/developing/creating-a-subgraph.mdx +++ b/website/pages/sv/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/tr/cookbook/arweave.mdx b/website/pages/tr/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/tr/cookbook/arweave.mdx +++ b/website/pages/tr/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/tr/cookbook/cosmos.mdx b/website/pages/tr/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/tr/cookbook/cosmos.mdx +++ b/website/pages/tr/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/tr/cookbook/near.mdx b/website/pages/tr/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/tr/cookbook/near.mdx +++ b/website/pages/tr/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/tr/cookbook/subgraph-debug-forking.mdx b/website/pages/tr/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/tr/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/tr/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/tr/developing/creating-a-subgraph.mdx b/website/pages/tr/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/tr/developing/creating-a-subgraph.mdx +++ b/website/pages/tr/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/uk/cookbook/arweave.mdx b/website/pages/uk/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/uk/cookbook/arweave.mdx +++ b/website/pages/uk/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/uk/cookbook/cosmos.mdx b/website/pages/uk/cookbook/cosmos.mdx index f454cfcf628b..d1c171814941 100644 --- a/website/pages/uk/cookbook/cosmos.mdx +++ b/website/pages/uk/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/uk/cookbook/near.mdx b/website/pages/uk/cookbook/near.mdx index 53d9b06c0a45..654e13633503 100644 --- a/website/pages/uk/cookbook/near.mdx +++ b/website/pages/uk/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/uk/cookbook/subgraph-debug-forking.mdx b/website/pages/uk/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/uk/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/uk/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/uk/developing/creating-a-subgraph.mdx b/website/pages/uk/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/uk/developing/creating-a-subgraph.mdx +++ b/website/pages/uk/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/ur/cookbook/arweave.mdx b/website/pages/ur/cookbook/arweave.mdx index bb55f351ca62..6a53ae342eef 100644 --- a/website/pages/ur/cookbook/arweave.mdx +++ b/website/pages/ur/cookbook/arweave.mdx @@ -166,7 +166,7 @@ graph deploy --node https://api.thegraph.com/deploy/ --ipfs https://api.thegraph حوالہ کے لیے سب گراف کی ایک مثال یہ ہے: -- [آرویو کے لیے سب گراف کی مثال](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [آرویو کے لیے سب گراف کی مثال](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/ur/cookbook/cosmos.mdx b/website/pages/ur/cookbook/cosmos.mdx index b6fe03308d55..2aa8570cd490 100644 --- a/website/pages/ur/cookbook/cosmos.mdx +++ b/website/pages/ur/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ class Any { یہ نوٹ کرنا ضروری ہے کہ کوزموس پیغامات سلسلہ کے لحاظ سے مخصوص ہوتے ہیں اور انہیں سیریلائزڈ [پروٹوکول بفرز](https://developers.google.com/protocol-buffers/) کی شکل میں سب گراف میں منتقل کیا جاتا ہے۔ > پے لوڈ۔ نتیجے کے طور پر، میسج ڈیٹا کو میپنگ فنکشن میں ڈی کوڈ کرنے کی ضرورت ہے اس سے پہلے کہ اس پر کارروائی کی جا سکے. -سب گراف میں پیغام کے ڈیٹا کو ڈی کوڈ کرنے کے طریقے کی ایک مثال [ یہاں](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts) مل سکتی ہے. +سب گراف میں پیغام کے ڈیٹا کو ڈی کوڈ کرنے کے طریقے کی ایک مثال [ یہاں](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts) مل سکتی ہے. ## کوزموس سب گراف بنانا اور تعمیر کرنا @@ -250,10 +250,10 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost حوالہ کے لیے ذیل میں کچھ مثالیں ہیں: -[بلاک فلٹرنگ کی مثال](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[بلاک فلٹرنگ کی مثال](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[ویلیڈیٹر کے انعامات کی مثال](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[ویلیڈیٹر کے انعامات کی مثال](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[ویلیڈیٹر ڈیلیگیشنز کی مثال](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[ویلیڈیٹر ڈیلیگیشنز کی مثال](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[اوسموسس ٹوکن سویپس کی مثال](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[اوسموسس ٹوکن سویپس کی مثال](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/ur/cookbook/near.mdx b/website/pages/ur/cookbook/near.mdx index 24bd70305d5b..4bb7090dd1f9 100644 --- a/website/pages/ur/cookbook/near.mdx +++ b/website/pages/ur/cookbook/near.mdx @@ -235,9 +235,9 @@ NEAR سب گراف کے لیے گراف کیو ایل اینڈ پوائنٹ کا حوالہ کے لیے ذیل میں کچھ مثالیں ہیں: -[NEAR بلاکس](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR بلاکس](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR ریسیپٹس](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR ریسیپٹس](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## عمومی سوالات diff --git a/website/pages/ur/cookbook/subgraph-debug-forking.mdx b/website/pages/ur/cookbook/subgraph-debug-forking.mdx index 39e52e658222..ce4f777c92a1 100644 --- a/website/pages/ur/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/ur/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ title: فورکس کا استعمال کرتے ہوۓ تیز اور آسان ڈ ## براۓ مہربانی، مجہے کچھ کوڈ دکھائیں! -سب گراف ڈیبگنگ پر توجہ مرکوز رکھنے کے لیے، آئیے چیزوں کو سادہ رکھیں اور [مثالی- سب گراف](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) کے ساتھ چلائیں۔ > ایتھرئم گریویٹی سمارٹ کنٹریکٹ کی انڈیکس کرنا. +سب گراف ڈیبگنگ پر توجہ مرکوز رکھنے کے لیے، آئیے چیزوں کو سادہ رکھیں اور [مثالی- سب گراف](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) کے ساتھ چلائیں۔ > ایتھرئم گریویٹی سمارٹ کنٹریکٹ کی انڈیکس کرنا. یہاں `Gravatar` کی انڈیکسنگ کے لیے بیان کردہ ہینڈلرز ہیں، بغیر کسی بگ کے: diff --git a/website/pages/ur/developing/creating-a-subgraph.mdx b/website/pages/ur/developing/creating-a-subgraph.mdx index aa9895f5e099..a275459d9529 100644 --- a/website/pages/ur/developing/creating-a-subgraph.mdx +++ b/website/pages/ur/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ Options: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/vi/cookbook/arweave.mdx b/website/pages/vi/cookbook/arweave.mdx index 3710f7632ba2..319ad2f760a7 100644 --- a/website/pages/vi/cookbook/arweave.mdx +++ b/website/pages/vi/cookbook/arweave.mdx @@ -166,7 +166,7 @@ The GraphQL endpoint for Arweave subgraphs is determined by the schema definitio Here is an example subgraph for reference: -- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## FAQ diff --git a/website/pages/vi/cookbook/cosmos.mdx b/website/pages/vi/cookbook/cosmos.mdx index 49d29dffdd8a..ef21e4bc0855 100644 --- a/website/pages/vi/cookbook/cosmos.mdx +++ b/website/pages/vi/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ You can find the full list of types for the Cosmos integration [here](https://gi It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://developers.google.com/protocol-buffers/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed. -An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts). +An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts). ## Creating and building a Cosmos subgraph @@ -250,10 +250,10 @@ Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`. Here are some example subgraphs for reference: -[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/vi/cookbook/near.mdx b/website/pages/vi/cookbook/near.mdx index 33ef5e56c213..6c2f253187ca 100644 --- a/website/pages/vi/cookbook/near.mdx +++ b/website/pages/vi/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, Here are some example subgraphs for reference: -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## FAQ diff --git a/website/pages/vi/cookbook/subgraph-debug-forking.mdx b/website/pages/vi/cookbook/subgraph-debug-forking.mdx index 5f214139646a..7ac3bf96ca10 100644 --- a/website/pages/vi/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/vi/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever: diff --git a/website/pages/vi/developing/creating-a-subgraph.mdx b/website/pages/vi/developing/creating-a-subgraph.mdx index b2e9801b28fb..f1709266536f 100644 --- a/website/pages/vi/developing/creating-a-subgraph.mdx +++ b/website/pages/vi/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ For the example subgraph, `subgraph.yaml` is: ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: diff --git a/website/pages/zh/cookbook/arweave.mdx b/website/pages/zh/cookbook/arweave.mdx index 3cc474722a8a..6ed57a8568f8 100644 --- a/website/pages/zh/cookbook/arweave.mdx +++ b/website/pages/zh/cookbook/arweave.mdx @@ -166,7 +166,7 @@ Arweave 子图的 GraphQL 端点由模式定义和现有的 API 接口决定。 下面是一个子图的例子，以供参考: -- [Arweave 的子图示例](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions) +- [Arweave 的子图示例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions) ## 常见问题 diff --git a/website/pages/zh/cookbook/cosmos.mdx b/website/pages/zh/cookbook/cosmos.mdx index 03ebe903355e..1119602898a6 100644 --- a/website/pages/zh/cookbook/cosmos.mdx +++ b/website/pages/zh/cookbook/cosmos.mdx @@ -178,7 +178,7 @@ class Any { 值得注意的是，Cosmos 消息是链特定的，以序列化的[协议缓冲](https://developers.google.com/protocol-buffers/)有效载荷的形式传递给子图。因此，在处理消息数据之前，需要在映射函数中对消息数据进行解码。 -如何在子图中解码消息数据的示例可以在[这里](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts)找到。 +如何在子图中解码消息数据的示例可以在[这里](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts)找到。 ## 创建和构建 Cosmos 子图 @@ -250,10 +250,10 @@ Osmosis 主网是 `osmosis-1`. Osmosis 当前测试网是`osmo-test-4`. 以下是一些示例子图供参考： -[区块过滤示例](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering) +[区块过滤示例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering) -[Validator 奖励示例](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards) +[Validator 奖励示例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards) -[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations) +[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations) -[Osmosis 代币交换示例](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps) +[Osmosis 代币交换示例](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps) diff --git a/website/pages/zh/cookbook/near.mdx b/website/pages/zh/cookbook/near.mdx index f723bdcbc97a..18e54ba64d24 100644 --- a/website/pages/zh/cookbook/near.mdx +++ b/website/pages/zh/cookbook/near.mdx @@ -235,9 +235,9 @@ The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, 以下是一些示例子图供参考： -[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example) +[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks) -[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example) +[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts) ## 常见问题 diff --git a/website/pages/zh/cookbook/subgraph-debug-forking.mdx b/website/pages/zh/cookbook/subgraph-debug-forking.mdx index 48ed6cb0d18a..b4b09ffc6480 100644 --- a/website/pages/zh/cookbook/subgraph-debug-forking.mdx +++ b/website/pages/zh/cookbook/subgraph-debug-forking.mdx @@ -18,7 +18,7 @@ In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph n ## Please, show me some code! -To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract. +To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract. 以下是索引 `Gravatar` 定义的处理程序，没有任何错误： diff --git a/website/pages/zh/developing/creating-a-subgraph.mdx b/website/pages/zh/developing/creating-a-subgraph.mdx index cd86514acec5..c13e613f911b 100644 --- a/website/pages/zh/developing/creating-a-subgraph.mdx +++ b/website/pages/zh/developing/creating-a-subgraph.mdx @@ -98,7 +98,7 @@ The contract `address` will be written to the `networks.json` for the relevant n ```yaml specVersion: 0.0.4 description: Gravatar for Ethereum -repository: https://github.com/graphprotocol/example-subgraphs +repository: https://github.com/graphprotocol/graph-tooling schema: file: ./schema.graphql dataSources: