-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Deprecation of arguments #270
Comments
I won't support this until it's in the spec. At that time, we can revisit it! If you have a specific use case, you could share it on facebook/graphql to help inform their decision. |
I think this has been roadmap by the graphql community graphql/graphql-spec#197 |
It looks like this lives here now: graphql/graphql-spec#525 |
this would be very useful for us (pro customer) |
#3015 adds support for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to have the ability to deprecate arguments,
like you can do with fields and enum values
Reference Deprecation of input fields,
This was proposed as part of the GraphQL specification, discussion is still ongoing
The text was updated successfully, but these errors were encountered: