Add support for generated @deprecated arguments from @GraphQLDeprecated #2075
+47
−1
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.
📝 Description
This PR enables support for using the
@GraphQLDeprecated
annotation on arguments, allowing the generated GraphQL schema to include the@deprecated
directive.Changes:
generateArgument.kt
to mark argument as deprecated if the DeprecationReason is present.Why?
The GraphQL spec now officially supports applying
@deprecated
on arguments, enabling better API evolution without breaking existing clients. This change aligns the library with the latest spec, giving developers a built-in way to signal argument deprecations.🔗 Related Issues
#1361