From 647f7036ec5995cf3ceb1df5d17284757549942a Mon Sep 17 00:00:00 2001 From: Alex Reilly Date: Mon, 18 Oct 2021 14:51:58 -0700 Subject: [PATCH] initial changes --- spec/Appendix B -- Grammar Summary.md | 2 +- spec/Section 7 -- Response.md | 9 +++++---- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/spec/Appendix B -- Grammar Summary.md b/spec/Appendix B -- Grammar Summary.md index 01c900a3f..0f927f3d1 100644 --- a/spec/Appendix B -- Grammar Summary.md +++ b/spec/Appendix B -- Grammar Summary.md @@ -45,7 +45,7 @@ Token :: - FloatValue - StringValue -Punctuator :: one of ! $ & ( ) ... : = @ [ ] { | } +Punctuator :: one of ! ? $ & ( ) ... : = @ [ ] { | } Name :: - NameStart NameContinue* [lookahead != NameContinue] diff --git a/spec/Section 7 -- Response.md b/spec/Section 7 -- Response.md index 071eb1058..11ed36639 100644 --- a/spec/Section 7 -- Response.md +++ b/spec/Section 7 -- Response.md @@ -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