Skip to content
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

Keywords should not be reserved #92

Closed
peldax opened this issue Nov 25, 2020 · 0 comments
Closed

Keywords should not be reserved #92

peldax opened this issue Nov 25, 2020 · 0 comments
Labels
Ctg - Spec incompatibility Something is not compliant with specification Status - On hold Some information is missing/not sure how to handle. Type - Enhancement New feature or request
Milestone

Comments

@peldax
Copy link
Member

peldax commented Nov 25, 2020

Currently, graphpinator does not allow fields/types/arguments to be named after executable document keywords null/true/false/query/mutation/subscription/on.

At the time of writing, GraphQL specification does not explicitly state whether is it valid or not, but according to the issue in GraphQL spec repository it should be possible.

@peldax peldax added Type - Enhancement New feature or request Ctg - Spec incompatibility Something is not compliant with specification Status - On hold Some information is missing/not sure how to handle. labels Nov 25, 2020
@peldax peldax changed the title Keywords are not reserved Keywords should not be reserved Nov 25, 2020
@peldax peldax added this to the v1.0 milestone May 29, 2021
@peldax peldax closed this as completed Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ctg - Spec incompatibility Something is not compliant with specification Status - On hold Some information is missing/not sure how to handle. Type - Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant