From 2a9f82f68d49ea68a227d583709c07860929caf1 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 27 Mar 2025 10:41:56 +0100 Subject: [PATCH 1/6] Add a provision for new request parameters --- spec/Section 6 -- Execution.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/spec/Section 6 -- Execution.md b/spec/Section 6 -- Execution.md index d88c685f9..9f97b6bc8 100644 --- a/spec/Section 6 -- Execution.md +++ b/spec/Section 6 -- Execution.md @@ -16,6 +16,9 @@ A GraphQL service generates a response from a request via execution. data available via a GraphQL Service. It is common for a GraphQL Service to always use the same initial value for every request. +As this specification evolves, new information may be added. Implementation +must ignore any value they do not recognize. + Given this information, the result of {ExecuteRequest(schema, document, operationName, variableValues, initialValue)} produces the response, to be formatted according to the Response section below. From 5a93620eadccb7fdab369ca769979164bd76af11 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 27 Mar 2025 10:42:31 +0100 Subject: [PATCH 2/6] format --- spec/Section 6 -- Execution.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/Section 6 -- Execution.md b/spec/Section 6 -- Execution.md index 9f97b6bc8..f07830c3e 100644 --- a/spec/Section 6 -- Execution.md +++ b/spec/Section 6 -- Execution.md @@ -16,8 +16,8 @@ A GraphQL service generates a response from a request via execution. data available via a GraphQL Service. It is common for a GraphQL Service to always use the same initial value for every request. -As this specification evolves, new information may be added. Implementation -must ignore any value they do not recognize. +As this specification evolves, new information may be added. Implementation must +ignore any value they do not recognize. Given this information, the result of {ExecuteRequest(schema, document, operationName, variableValues, initialValue)} produces the response, to be From 35ab3387c728b6bd0f363c0284169a00349c54a9 Mon Sep 17 00:00:00 2001 From: Lee Byron Date: Thu, 3 Apr 2025 11:30:18 -0700 Subject: [PATCH 3/6] Update Section 6 -- Execution.md --- spec/Section 6 -- Execution.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/spec/Section 6 -- Execution.md b/spec/Section 6 -- Execution.md index f07830c3e..b5e933d44 100644 --- a/spec/Section 6 -- Execution.md +++ b/spec/Section 6 -- Execution.md @@ -16,17 +16,19 @@ A GraphQL service generates a response from a request via execution. data available via a GraphQL Service. It is common for a GraphQL Service to always use the same initial value for every request. -As this specification evolves, new information may be added. Implementation must -ignore any value they do not recognize. - Given this information, the result of {ExecuteRequest(schema, document, operationName, variableValues, initialValue)} produces the response, to be formatted according to the Response section below. +A GraphQL service must ignore unrecognized information in a request. This allows +a service to remain resilient to future changes in future versions of this +specification. + Note: GraphQL requests do not require any specific serialization format or transport mechanism. Message serialization and transport mechanisms should be chosen by the implementing service. + ## Executing Requests To execute a request, the executor must have a parsed {Document} and a selected From c133ab24eced5a5924df69a962bb7b9e58a1210f Mon Sep 17 00:00:00 2001 From: Lee Byron Date: Thu, 3 Apr 2025 11:30:34 -0700 Subject: [PATCH 4/6] Update Section 6 -- Execution.md --- spec/Section 6 -- Execution.md | 1 - 1 file changed, 1 deletion(-) diff --git a/spec/Section 6 -- Execution.md b/spec/Section 6 -- Execution.md index b5e933d44..a17a45b7a 100644 --- a/spec/Section 6 -- Execution.md +++ b/spec/Section 6 -- Execution.md @@ -28,7 +28,6 @@ Note: GraphQL requests do not require any specific serialization format or transport mechanism. Message serialization and transport mechanisms should be chosen by the implementing service. - ## Executing Requests To execute a request, the executor must have a parsed {Document} and a selected From 64b5af314bd13f3638dd4561b252930aaa0d3b02 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Fri, 4 Apr 2025 00:06:19 +0200 Subject: [PATCH 5/6] Update spec/Section 6 -- Execution.md Co-authored-by: Benjie --- spec/Section 6 -- Execution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/Section 6 -- Execution.md b/spec/Section 6 -- Execution.md index a17a45b7a..94b25bb91 100644 --- a/spec/Section 6 -- Execution.md +++ b/spec/Section 6 -- Execution.md @@ -21,7 +21,7 @@ operationName, variableValues, initialValue)} produces the response, to be formatted according to the Response section below. A GraphQL service must ignore unrecognized information in a request. This allows -a service to remain resilient to future changes in future versions of this +a service to remain resilient to changes in future versions of this specification. Note: GraphQL requests do not require any specific serialization format or From f91ca5183d54567f215c8d42f6c0fa3e7d4e732e Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Thu, 17 Apr 2025 11:39:40 +0200 Subject: [PATCH 6/6] format --- spec/Section 6 -- Execution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/Section 6 -- Execution.md b/spec/Section 6 -- Execution.md index 94b25bb91..3716c71fe 100644 --- a/spec/Section 6 -- Execution.md +++ b/spec/Section 6 -- Execution.md @@ -21,7 +21,7 @@ operationName, variableValues, initialValue)} produces the response, to be formatted according to the Response section below. A GraphQL service must ignore unrecognized information in a request. This allows -a service to remain resilient to changes in future versions of this +a service to remain resilient to changes in future versions of this specification. Note: GraphQL requests do not require any specific serialization format or