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