File tree Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -212,18 +212,18 @@ type MyMutationRootType {
212
212
**Default Root Operation Type Names **
213
213
214
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
215
+ _default operation type name_ for the {`query `}, {`mutation `}, and
216
216
{`subscription `} root types are {"Query" }, {"Mutation" }, and {"Subscription" }
217
217
respectively .
218
218
219
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.
220
+ root type present uses its respective _default operation type name_ and no other
221
+ type uses a default operation type name.
222
222
223
223
Likewise, when representing a GraphQL schema using the type system definition
224
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.
225
+ its respective _default operation type name_ and no other type uses a default
226
+ operation type name.
227
227
228
228
This example describes a valid complete GraphQL schema, despite not explicitly
229
229
including a {`schema`} definition . The {"Query" } type is presumed to be the
You can’t perform that action at this time.
0 commit comments