Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grammar: fix comma splices and similar minor issues #331

Merged
merged 2 commits into from
Feb 26, 2025
Merged

grammar: fix comma splices and similar minor issues #331

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e72025d
grammar: fix comma splices and similar minor issues
glasser Feb 19, 2025
f0e2efe
format
martinbonnin Feb 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions spec/GraphQLOverHTTP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,15 @@ 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
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)
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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.

Expand Down