Skip to content

Editorial: Clarity about subject being a GraphQL service or system #965

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

Merged
merged 1 commit into from
Jun 21, 2022
Merged

Editorial: Clarity about subject being a GraphQL service or system #965

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions spec/Section 5 -- Validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Validation

GraphQL does not just verify if a request is syntactically correct, but also
ensures that it is unambiguous and mistake-free in the context of a given
GraphQL schema.
A GraphQL service does not just verify if a request is syntactically correct,
but also ensures that it is unambiguous and mistake-free in the context of a
given GraphQL schema.

An invalid request is still technically executable, and will always produce a
stable result as defined by the algorithms in the Execution section, however
Expand Down
4 changes: 2 additions & 2 deletions spec/Section 6 -- Execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Execution

GraphQL generates a response from a request via execution.
A GraphQL service generates a response from a request via execution.

:: A _request_ for execution consists of a few pieces of information:

Expand Down Expand Up @@ -174,7 +174,7 @@ Subscribe(subscription, schema, variableValues, initialValue):
{MapSourceToResponseEvent(sourceStream, subscription, schema, variableValues)}
- Return {responseStream}.

Note: In large scale subscription systems, the {Subscribe()} and
Note: In a large-scale subscription system, the {Subscribe()} and
{ExecuteSubscriptionEvent()} algorithms may be run on separate services to
maintain predictable scaling properties. See the section below on Supporting
Subscriptions at Scale.
Expand Down