Skip to content

Commit b9f1f33

Browse files
committed
Reformat
1 parent f8fd141 commit b9f1f33

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

spec/Section 5 -- Validation.md

+10-7
Original file line numberDiff line numberDiff line change
@@ -338,21 +338,24 @@ must provide the operation name as described in {GetOperation()}.
338338

339339
For each operation definition in the document:
340340

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.
343345

344346
#### Explanatory Text
345347

346348
A schema defines the root operation types that it supports. Any document that
347349
contains an operation of a type unsupported by the schema is invalid, since such
348350
an operation cannot be executed.
349351

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.
353356

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:
356359

357360
```graphql example
358361
mutation {

0 commit comments

Comments
 (0)