-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Question about grammar #918
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Link to spec screenshotted above: https://spec.graphql.org/draft/#sec-Language.Arguments Link to source: https://github.com/graphql/graphql-spec/blame/main/spec/Section%202%20--%20Language.md#L410
The For the Introduced via this PR: https://github.com/graphql/graphql-spec/pull/90/files But specifically this commit: eeb1a2c Description: "Ensure directives cannot reference variables in SDL" This seems to be subscripting indicating that when you reference To be more explicit, the following would be invalid:
And that is enforced at a grammar level. |
The graphql spec (https://spec.graphql.org/draft/#sec-Appendix-Grammar-Summary.Source-Text) declares that in some location a value cannot be a variable. This is especially the case in the schema definition language, where setting the values of directive arguments to a variable is not permitted. Also in executable documents, setting the default value of a variable definition to a variable is not permitted. See graphql/graphql-spec#918 (comment) for more on this.
The graphql spec (https://spec.graphql.org/draft/#sec-Appendix-Grammar-Summary.Source-Text) declares that in some location a value cannot be a variable. This is especially the case in the schema definition language, where setting the values of directive arguments to a variable is not permitted. Also in executable documents, setting the default value of a variable definition to a variable is not permitted. See graphql/graphql-spec#918 (comment) for more on this.
Hi. I have long wanted to ask what these modifiers mean. I did not find explanations in the specification. Thanks.
The text was updated successfully, but these errors were encountered: