You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
scala.@deprecatedshould be used instead of Java's @Deprecated.
Message should be supported in the deprecated directive, especially for Kotlin. This value is required, now we've used a default value for it, but that's not a good way. should be replaced.
It may be necessary to refactor XXDefinition.deprecated. It involves multilingualism, and it is not sure how to isolate it for the time being. After all, Java doesn't support the message field in Deprecated annotation.
And more considerations for default graphql Directive?
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
scala.@deprecated
should be used instead of Java's@Deprecated
.deprecated
directive, especially for Kotlin. This value is required, now we've used a default value for it, but that's not a good way. should be replaced.It may be necessary to refactor
XXDefinition.deprecated
. It involves multilingualism, and it is not sure how to isolate it for the time being. After all, Java doesn't support the message field in Deprecated annotation.And more considerations for default graphql Directive?
The text was updated successfully, but these errors were encountered: