@@ -338,21 +338,24 @@ must provide the operation name as described in {GetOperation()}.
338
338
339
339
For each operation definition in the document:
340
340
341
- - Let {operationType} be the type of the operation (` query ` , ` mutation ` , or ` subscription ` ).
342
- - The corresponding _ root operation type_ for {operationType} must be defined in the schema.
341
+ - Let {operationType} be the type of the operation (` query ` , ` mutation ` , or
342
+ ` subscription ` ).
343
+ - The corresponding _ root operation type_ for {operationType} must be defined in
344
+ the schema.
343
345
344
346
#### Explanatory Text
345
347
346
348
A schema defines the root operation types that it supports. Any document that
347
349
contains an operation of a type unsupported by the schema is invalid, since such
348
350
an operation cannot be executed.
349
351
350
- While query operations are required for all schemas, mutation and subscription operations
351
- are optional. If the schema does not include the necessary type for a mutation or subscription
352
- operation defined in the document, it will be considered invalid.
352
+ While query operations are required for all schemas, mutation and subscription
353
+ operations are optional. If the schema does not include the necessary type for a
354
+ mutation or subscription operation defined in the document, it will be
355
+ considered invalid.
353
356
354
- For example, the following document is valid if the schema includes a Mutation type, but
355
- invalid if it does not:
357
+ For example, the following document is valid if the schema includes a Mutation
358
+ type, but invalid if it does not:
356
359
357
360
``` graphql example
358
361
mutation {
0 commit comments