Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update links to the example-subgraph repo #175

Merged
merged 3 commits into from
Jul 27, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/en/cookbook/arweave.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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-subgraph/tree/arweave-blocks-transactions)
- [Example subgraph for Arweave](https://github.com/graphprotocol/example-subgraphs/tree/main/arweave/blocks-transactions)

## FAQ

Expand Down
10 changes: 5 additions & 5 deletions pages/en/cookbook/cosmos.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ Each type of handler will receive a different type based on the relevant data. F

`EventData` is passed to the eventHandler.

`TransactionData` is passed to the transactionHandler. Transactions will need to be decoded in the subgraph, [here](https://github.com/graphprotocol/example-subgraph/blob/cosmos-validator-delegations/src/decoding.ts) is an example on how it can be done.
`TransactionData` is passed to the transactionHandler. Transactions will need to be decoded in the subgraph, [here](https://github.com/graphprotocol/example-subgraphs/blob/main/cosmos/validator-delegations/src/decoding.ts) is an example on how it can be done.

## Creating and building a Cosmos subgraph

Expand Down Expand Up @@ -223,10 +223,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-subgraph/tree/cosmos-block-filtering)
[Block Filtering Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/block-filtering)

[Validator Rewards Example](https://github.com/graphprotocol/example-subgraph/tree/cosmos-validator-rewards)
[Validator Rewards Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-rewards)

[Validator Delegations Example](https://github.com/graphprotocol/example-subgraph/tree/cosmos-validator-delegations)
[Validator Delegations Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/validator-delegations)

[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraph/tree/osmosis-token-swaps)
[Osmosis Token Swaps Example](https://github.com/graphprotocol/example-subgraphs/tree/main/cosmos/osmosis-token-swaps)
4 changes: 2 additions & 2 deletions pages/en/cookbook/near.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -222,9 +222,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-subgraph/tree/near-blocks-example)
[NEAR Blocks](https://github.com/graphprotocol/example-subgraphs/tree/main/near/blocks-example)

[NEAR Receipts](https://github.com/graphprotocol/example-subgraph/tree/near-receipts-example)
[NEAR Receipts](https://github.com/graphprotocol/example-subgraphs/tree/main/near/receipts-example)

## FAQ

Expand Down
2 changes: 1 addition & 1 deletion pages/en/cookbook/subgraph-debug-forking.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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-subgraph) 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/example-subgraphs/tree/main/ethereum/gravatar) indexing the Ethereum Gravity smart contract.

Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever:

Expand Down
2 changes: 1 addition & 1 deletion pages/en/developing/creating-a-subgraph.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ For the example subgraph, `subgraph.yaml` is:
```yaml
specVersion: 0.0.4
description: Gravatar for Ethereum
repository: https://github.com/graphprotocol/example-subgraph
repository: https://github.com/graphprotocol/example-subgraphs
schema:
file: ./schema.graphql
dataSources:
Expand Down