-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Allow deprecation of input values (field args, directive args, input fields) #805
Conversation
Absinthe already supported deprecating args/input fields and this PR exposes that in the introspection query to match the spec. Also some tests were added for deprecating stuff. See graphql/graphql-spec#805 for the spec update
51f2fed
to
f96b562
Compare
@smitt04 would you mind signing the CLA (linked above) for your contribution? |
I've applied some editorial here, and I think this is good to go from a spec text point of view. The previous PR was moved to RFC2 and as discussed here graphql/graphql-wg#639 we have some next steps. Notably on the JS side there is a missing piece compared to what this RFC proposes, tracked here: graphql/graphql-js#3048 There was also a question about validation being correct or having the right "breaking/dangerous changes" protections in place. @IvanGoncharov or other authors here have context on that? |
e5d241d
to
6c81ed8
Compare
@IvanGoncharov Do we have any validation rule changes so that it is invalid to deprecate required arguments or required input fields? |
👋 @leebyron - regarding:
Now that the CLA has been signed, is there anything outstanding that is preventing this from being merged? |
graphql/graphql-spec#805 changed the GraphQL spec to allow deprecation on argument definitions and input field definitions.
It is now safe to remove this warning, this is merged and isn't a proposal anymore, see more graphql/graphql-spec#805
Continuation of #525 by @smitt04
Revisits #197 by @dylanahsmith