Skip to content

Commit 9bfc339

Browse files
committed
Alternative wording
1 parent 51dae85 commit 9bfc339

File tree

1 file changed

+11
-7
lines changed

1 file changed

+11
-7
lines changed

spec/Section 3 -- Type System.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -211,15 +211,19 @@ type MyMutationRootType {
211211

212212
**Default Root Operation Type Names**
213213

214-
While any type can be the root operation type for a GraphQL operation, the type
215-
system definition language can omit the schema definition when each of the
216-
{`query`}, {`mutation`}, and {`subscription`} root types are named {"Query"},
217-
{"Mutation"}, and {"Subscription"} respectively (if present), and these names
218-
are only used for root types.
214+
:: While any type can be the root operation type for a GraphQL operation, the
215+
_default root operation type name_ for the {`query`}, {`mutation`}, and
216+
{`subscription`} root types are {"Query"}, {"Mutation"}, and {"Subscription"}
217+
respectively.
218+
219+
The type system definition language can omit the schema definition when each
220+
root type present uses its respective _default root operation type name_ and no
221+
other type uses a default root operation type name.
219222

220223
Likewise, when representing a GraphQL schema using the type system definition
221-
language, a schema definition should be omitted if it only uses these default
222-
root operation type names as the names of the respective root types.
224+
language, a schema definition should be omitted if each root type present uses
225+
its respective _default root operation type name_ and no other type uses a
226+
default root operation type name.
223227

224228
This example describes a valid complete GraphQL schema, despite not explicitly
225229
including a {`schema`} definition. The {"Query"} type is presumed to be the

0 commit comments

Comments
 (0)