Skip to content

Commit

Permalink
Update docs/execution-pipeline.md
Browse files Browse the repository at this point in the history
Thank @xperiandri

Co-authored-by: Andrii Chebukin <[email protected]>
  • Loading branch information
valbers and xperiandri authored Dec 14, 2024
1 parent 5eef758 commit 5812c65
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/execution-pipeline.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ The execution phase can be performed using one of the two strategies:
The result of a GraphQL query execution is a dictionary with resolved values. This dictionary contains the following fields:

- `documentId`: which is the hash code of the query's AST document - it can be used to implement execution plan caching (persistent queries).
- `data`: with a formated GraphQL response matching the requested query.
- `errors`: optional. If it has been provided, it will contain a list of errors that occured during query execution.
- `data`: optional, a formatted GraphQL response matching the requested query (`KeyValuePair seq`). Absent in case of an error that does not allow continuing processing and returning any GraphQL results.
- `errors`: optional, contains a list of errors (`GQLProblemDetails`) that occurred during query execution.

This result can then be serialized and returned to the client.

0 comments on commit 5812c65

Please sign in to comment.