File tree Expand file tree Collapse file tree 2 files changed +6
-5
lines changed Expand file tree Collapse file tree 2 files changed +6
-5
lines changed Original file line number Diff line number Diff line change @@ -45,7 +45,7 @@ Token ::
4545 - FloatValue
4646 - StringValue
4747
48- Punctuator :: one of ! $ & ( ) ... : = @ [ ] { | }
48+ Punctuator :: one of ! ? $ & ( ) ... : = @ [ ] { | }
4949
5050Name ::
5151 - NameStart NameContinue* [lookahead != NameContinue]
Original file line number Diff line number Diff 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
169170For example, if the `name` field from above had declared a `Non-Null` return
170171type in the schema, the result would look different but the error reported would
You can’t perform that action at this time.
0 commit comments