Skip to content

Commit

Permalink
initial changes
Browse files Browse the repository at this point in the history
  • Loading branch information
twof committed Oct 18, 2021
1 parent ffb1fcc commit 647f703
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 5 deletions.
2 changes: 1 addition & 1 deletion spec/Appendix B -- Grammar Summary.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ Token ::
- FloatValue
- StringValue

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

Name ::
- NameStart NameContinue* [lookahead != NameContinue]
Expand Down
9 changes: 5 additions & 4 deletions spec/Section 7 -- Response.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,10 +161,11 @@ The response might look like:
}
```

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

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

0 comments on commit 647f703

Please sign in to comment.