From 48827ec279391e9d3fbbf202815b3f9b1ac2818f Mon Sep 17 00:00:00 2001 From: Vincent Cloutier Date: Mon, 8 Aug 2022 18:20:14 -0400 Subject: [PATCH] docs: fix dead link (#25496) --- docs/_rpc/graphql.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_rpc/graphql.md b/docs/_rpc/graphql.md index 8cb82f4ebb..613eaf9b1a 100644 --- a/docs/_rpc/graphql.md +++ b/docs/_rpc/graphql.md @@ -3,7 +3,7 @@ title: GraphQL Server sort_key: C --- -In addition to the [JSON-RPC APIs](../rpc/server), Geth supports the GraphQL API as specified by [EIP-1767](eip-1767). GraphQL lets you specify which fields of an objects you need as part of the query, eliminating the extra load on the client for filling in fields which are not needed. It also allows for combining several traditional JSON-RPC requests into one query which translates into less overhead and more performance. +In addition to the [JSON-RPC APIs](../rpc/server), Geth supports the GraphQL API as specified by [EIP-1767](https://eips.ethereum.org/EIPS/eip-1767). GraphQL lets you specify which fields of an objects you need as part of the query, eliminating the extra load on the client for filling in fields which are not needed. It also allows for combining several traditional JSON-RPC requests into one query which translates into less overhead and more performance. The GraphQL endpoint piggybacks on the HTTP transport used by JSON-RPC. Hence you'll have to enable and configure the relevant `--http` flags, and the `--graphql` flag itself: