Fixing some bugs regarding transformation of annotation 'java.lang.Deprecated' to graphQL's 'Deprecated'. directive. #1897
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.
fixes:#1896
/cc @jmartisk
Changes:
Changes:
Optional<DirectiveInstance>
type instead of the raw type. This change eliminates situations where the method could returnnull
or a list, as was the case withDeprecatedDirectivesHelper
. Since thejava.lang.Deprecated
is non repeatable annotation.java.lang.Deprecated
during schema generation via thesmallrye-graphql-maven-plugin
goal:generating-schema
. The issue stemmed from the fact thatGenerateSchemaMojo
did not scan thesmallrye-graphql-api
, where the GraphQL Deprecated annotation was defined.java.lang.Deprecated
from operations (high-level fields), enum values, and field definitions of an output type. This addition complements the existing implementation for attribute definitions and input type field definitions.tests: quarkusio/quarkus@204c115