hiro/apollo-server
1
0
Fork 0
mirror of https://github.com/vale981/apollo-server synced 2025-03-06 10:11:40 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

s/name/identifier/ for named operations.

Browse source
This commit is contained in:
Jesse Rosenberger 2018-04-24 15:06:59 +03:00
parent 84c41ce21a
commit 1b9d32ddb0
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/source/essentials/schema.md
View file

@ -209,7 +209,7 @@ This makes SDL-generation even easier since many GraphQL tools auto-complete fie
When sending the queries and mutations in the above examples, we've used either `query { ... }` or `mutation { ... }` respectively. While this is fine, and particularly convenient when running queries by hand, it makes sense to name the operation in order to quickly identify operations during debugging or to aggregate similar operations together for application performance metrics, for example, when using [Apollo Engine]() to monitor an API.
Operations can be named by placing a name after the `query` or `operation` keyword, as in:
Operations can be named by placing an identifier after the `query` or `operation` keyword, as in:
```graphql
query HomepageBookListing {