Skip to content

Commit 9c62584

Browse files
authored
Update Section 5 -- Validation.md
1 parent 5d56a15 commit 9c62584

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

spec/Section 5 -- Validation.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ tool should report validation errors and not allow the
1818
formulation or execution of requests known to be invalid at that given point in
1919
time.
2020

21-
**Type system evolution**
21+
**Type System Evolution**
2222

2323
As GraphQL type system schema evolves over time by adding new types and new
2424
fields, it is possible that a request which was previously valid could later
@@ -1082,7 +1082,7 @@ fragment ownerFragment on Human {
10821082
}
10831083
```
10841084

1085-
#### Fragment spread is possible
1085+
#### Fragment Spread is Possible
10861086

10871087
**Formal Specification**
10881088

@@ -1107,7 +1107,7 @@ type matches the type condition. They also are spread within the context of a
11071107
parent type. A fragment spread is only valid if its type condition could ever
11081108
apply within the parent type.
11091109

1110-
##### Object Spreads In Object Scope
1110+
##### Object Spreads in Object Scope
11111111

11121112
In the scope of an object type, the only valid object type fragment spread is
11131113
one that applies to the same type that is in scope.
@@ -1170,7 +1170,7 @@ that if one inspected the contents of the {CatOrDogNameFragment} you could note
11701170
that no valid results would ever be returned. However we do not specify this as
11711171
invalid because we only consider the fragment declaration, not its body.
11721172

1173-
##### Object Spreads In Abstract Scope
1173+
##### Object Spreads in Abstract Scope
11741174

11751175
Union or interface spreads can be used within the context of an object type
11761176
fragment, but only if the object type is one of the possible types of that
@@ -1960,7 +1960,7 @@ query listToNonNullList($booleanList: [Boolean]) {
19601960
This would fail validation because a `[T]` cannot be passed to a `[T]!`.
19611961
Similarly a `[T]` cannot be passed to a `[T!]`.
19621962

1963-
**Allowing optional variables when default values exist**
1963+
**Allowing Optional Variables when Default Values Exist**
19641964

19651965
A notable exception to typical variable type compatibility is allowing a
19661966
variable definition with a nullable type to be provided to a non-null location

0 commit comments

Comments
 (0)