Skip to content

Commit 35ab338

Browse files
authored
Update Section 6 -- Execution.md
1 parent 5a93620 commit 35ab338

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

spec/Section 6 -- Execution.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,17 +16,19 @@ A GraphQL service generates a response from a request via execution.
1616
data available via a GraphQL Service. It is common for a GraphQL Service to
1717
always use the same initial value for every request.
1818

19-
As this specification evolves, new information may be added. Implementation must
20-
ignore any value they do not recognize.
21-
2219
Given this information, the result of {ExecuteRequest(schema, document,
2320
operationName, variableValues, initialValue)} produces the response, to be
2421
formatted according to the Response section below.
2522

23+
A GraphQL service must ignore unrecognized information in a request. This allows
24+
a service to remain resilient to future changes in future versions of this
25+
specification.
26+
2627
Note: GraphQL requests do not require any specific serialization format or
2728
transport mechanism. Message serialization and transport mechanisms should be
2829
chosen by the implementing service.
2930

31+
3032
## Executing Requests
3133

3234
To execute a request, the executor must have a parsed {Document} and a selected

0 commit comments

Comments
 (0)