You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/execution-pipeline.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,8 +52,8 @@ The execution phase can be performed using one of the two strategies:
52
52
53
53
The result of a GraphQL query execution is a `GQLResponse` object with the following fields:
54
54
55
-
-`documentId`: which is the hash code of the query's AST document - it can be used to implement execution plan caching (persistent queries).
55
+
-`documentId`: deterministic SHA-256 hash (lowercase hex string) of the canonical query document - it can be used to implement execution plan caching (persistent queries).
56
56
-`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.
57
57
-`errors`: optional, contains a list of errors (`GQLProblemDetails`) that occurred during query execution.
58
58
59
-
This result can then be serialized and returned to the client.
59
+
This result can then be serialized and returned to the client.
0 commit comments