feat: Adding deprecation fields to InputValue #553
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will support deprecated directive on InputValue as defined in https://spec.graphql.org/September2025/#sec--deprecated
tomhoule
requested changes
Oct 30, 2025
New fields should have default serde values in order to keep backward compatibility.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding support to deprecated directive on
InputValueas defined in https://spec.graphql.org/September2025/#sec--deprecated.This will also help us to solve a bug on http://github.com/apollographql/rover where the rover graph introspection does not correctly fetch the
@deprecateddirectives from the introspected schema.