From e72025dda258344d3dc934d7b96c41ad0365290d Mon Sep 17 00:00:00 2001 From: David Glasser Date: Wed, 19 Feb 2025 09:08:18 -0800 Subject: [PATCH 1/2] grammar: fix comma splices and similar minor issues --- spec/GraphQLOverHTTP.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/spec/GraphQLOverHTTP.md b/spec/GraphQLOverHTTP.md index d126f889..5f1339be 100644 --- a/spec/GraphQLOverHTTP.md +++ b/spec/GraphQLOverHTTP.md @@ -14,14 +14,14 @@ rely on a draft in a production GraphQL Service. This specification details how GraphQL should be served and consumed over HTTP in order to maximize interoperability between clients, servers and tools. This specification does not override or replace the -[GraphQL specification](https://spec.graphql.org), it extends it to cover the +[GraphQL specification](https://spec.graphql.org); it extends it to cover the topic of serving GraphQL services over HTTP. If any statement or algorithm in this specification appears to conflict with the GraphQL specification, the behavior detailed in the GraphQL specification should be used (and an issue raised). The [GraphQL specification](https://spec.graphql.org) deliberately does not -specify the transport layer, however HTTP is the most common choice when serving +specify the transport layer; however, HTTP is the most common choice when serving GraphQL to remote clients due to its ubiquity. Previous to this specification, the article @@ -105,7 +105,7 @@ and a GraphQL response in an HTTP response. Specification compliant HTTP server unless the context indicates otherwise. The role of a _server_ is to provide a _client_ access to one or more GraphQL -services over HTTP. A _server_ is not a _GraphQL service_, it is a GraphQL +services over HTTP. A _server_ is not a _GraphQL service_; it is a GraphQL service host. :: In this document, the term _client_ refers to a GraphQL over HTTP @@ -373,8 +373,8 @@ When encoded in JSON, a _GraphQL-over-HTTP request_ is encoded as a JSON object names and the values of which are the variable values - {extensions} - an optional object (map) -All other property names are reserved for future expansion; if implementors need -to add additional information to a request they MUST do so via other means, the +All other property names are reserved for future expansion. If implementors need +to add additional information to a request they MUST do so via other means; the RECOMMENDED approach is to add an implementor-scoped entry to the {extensions} object. From f0e2efef5ecf24007830470189c87b669f1868b2 Mon Sep 17 00:00:00 2001 From: Martin Bonnin Date: Tue, 25 Feb 2025 16:25:09 +0100 Subject: [PATCH 2/2] format --- spec/GraphQLOverHTTP.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/GraphQLOverHTTP.md b/spec/GraphQLOverHTTP.md index 5f1339be..8e182c8b 100644 --- a/spec/GraphQLOverHTTP.md +++ b/spec/GraphQLOverHTTP.md @@ -21,8 +21,8 @@ behavior detailed in the GraphQL specification should be used (and an issue raised). The [GraphQL specification](https://spec.graphql.org) deliberately does not -specify the transport layer; however, HTTP is the most common choice when serving -GraphQL to remote clients due to its ubiquity. +specify the transport layer; however, HTTP is the most common choice when +serving GraphQL to remote clients due to its ubiquity. Previous to this specification, the article [Serving over HTTP](https://graphql.org/learn/serving-over-http)