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 ::
45
45
- FloatValue
46
46
- StringValue
47
47
48
- Punctuator :: one of ! $ & ( ) ... : = @ [ ] { | }
48
+ Punctuator :: one of ! ? $ & ( ) ... : = @ [ ] { | }
49
49
50
50
Name ::
51
51
- NameStart NameContinue* [ lookahead != NameContinue]
Original file line number Diff line number Diff line change @@ -161,10 +161,11 @@ The response might look like:
161
161
}
162
162
```
163
163
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.
168
169
169
170
For example, if the ` name ` field from above had declared a ` Non-Null ` return
170
171
type 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