Skip to content

Commit 849c7ac

Browse files
committed
initial changes
1 parent ffb1fcc commit 849c7ac

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
@@ -45,7 +45,7 @@ Token ::
4545
- FloatValue
4646
- StringValue
4747

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

5050
Name ::
5151
- NameStart NameContinue* [lookahead != NameContinue]

spec/Section 7 -- Response.md

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

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

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

0 commit comments

Comments
 (0)