Skip to content

Commit 52cc30c

Browse files
authored
Merge pull request #10283 from AbhiGulati/patch-1
Fix broken link for subgraph manifest
2 parents 740611b + b84100f commit 52cc30c

File tree

1 file changed

+4
-4
lines changed
  • src/content/developers/tutorials/the-graph-fixing-web3-data-querying

1 file changed

+4
-4
lines changed

src/content/developers/tutorials/the-graph-fixing-web3-data-querying/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ You can define multiple contracts and handlers here. A typical setup would have
126126

127127
For convenience reasons you also might want to use a template tool like mustache. Then you create a `subgraph.template.yaml` and insert the addresses based on the latest deployments. For a more advanced example setup, see for example the [Aave subgraph repo](https://github.com/aave/aave-protocol/tree/master/thegraph).
128128

129-
And the full documentation can be seen here: https://thegraph.com/docs/define-a-subgraph#the-subgraph-manifest.
129+
And the full documentation can be seen [here](https://thegraph.com/docs/en/developing/creating-a-subgraph/#the-subgraph-manifest).
130130

131131
```yaml
132132
specVersion: 0.0.1
@@ -169,7 +169,7 @@ The schema is the GraphQL data definition. It will allow you to define which ent
169169
- BigInt
170170
- BigDecimal
171171

172-
You can also use entities as type to define relationships. In our example we define a 1-to-many relationship from player to bets. The ! means the value can't be empty. The full documentation can be seen here: https://thegraph.com/docs/define-a-subgraph#the-graphql-schema.
172+
You can also use entities as type to define relationships. In our example we define a 1-to-many relationship from player to bets. The ! means the value can't be empty. The full documentation can be seen [here](https://thegraph.com/docs/define-a-subgraph#the-graphql-schema).
173173

174174
```graphql
175175
type Bet @entity {
@@ -295,13 +295,13 @@ But we're missing one last piece of the puzzle and that's the server. You can ei
295295

296296
### Graph Explorer: The hosted service {#graph-explorer-the-hosted-service}
297297

298-
The easiest way is to use the hosted service. Follow the instructions [here](https://thegraph.com/docs/deploy-a-subgraph) to deploy a subgraph. For many projects you can actually find existing subgraphs in the explorer at https://thegraph.com/explorer/.
298+
The easiest way is to use the hosted service. Follow the instructions [here](https://thegraph.com/docs/deploy-a-subgraph) to deploy a subgraph. For many projects you can actually find existing subgraphs in the [explorer](https://thegraph.com/explorer/).
299299

300300
![The Graph-Explorer](./thegraph-explorer.png)
301301

302302
### Running your own node {#running-your-own-node}
303303

304-
Alternatively you can run your own node: https://github.com/graphprotocol/graph-node#quick-start. One reason to do this might be using a network that's not supported by the hosted service. Currently supported are Mainnet, Kovan, Rinkeby, Ropsten, Goerli, PoA-Core, xDAI and Sokol.
304+
Alternatively you can run your own node. Docs [here](https://github.com/graphprotocol/graph-node#quick-start). One reason to do this might be using a network that's not supported by the hosted service. Currently supported are Mainnet, Kovan, Rinkeby, Ropsten, Goerli, PoA-Core, xDAI and Sokol.
305305

306306
## The decentralized future {#the-decentralized-future}
307307

0 commit comments

Comments
 (0)