Skip to content

Commit 8a13c8f

Browse files
committed
initial changes
1 parent 78ccda7 commit 8a13c8f

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed

spec/Appendix B -- Grammar Summary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Token ::
4848
- FloatValue
4949
- StringValue
5050

51-
Punctuator :: one of ! $ & ( ) ... : = @ [ ] { | }
51+
Punctuator :: one of ! ? $ & ( ) ... : = @ [ ] { | }
5252

5353
Name ::
5454

spec/Section 7 -- Response.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -160,10 +160,11 @@ The response might look like:
160160
}
161161
```
162162

163-
If the field which experienced an error was declared as `Non-Null`, the `null`
164-
result will bubble up to the next nullable field. In that case, the `path` for
165-
the error should include the full path to the result field where the error was
166-
raised, even if that field is not present in the response.
163+
If the field which experienced an error was declared as `Non-Null` or designated
164+
`Non-Null` in the query document, the `null` result will propagate to the
165+
next nullable field. In that case, the `path` for the error should include
166+
the full path to the result field where the error was raised, even if that
167+
field is not present in the response.
167168

168169
For example, if the `name` field from above had declared a `Non-Null` return
169170
type in the schema, the result would look different but the error reported would

0 commit comments

Comments
 (0)