-
-
Notifications
You must be signed in to change notification settings - Fork 758
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
Fixed deprecation handling. #876
Conversation
The schema serialization is now also tweaked and will not handle is deprecated as a special case anymore. Moreover, directives now do not serialize null arguments anymore. This makes the serialized schema much cleaner. |
OK, there were a lot of tests to update due to the schema serializer changes. But I think the printed schemas are now much nicer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, have a couple of minor questions.
The deprecation directive was not implemented as specified in the spec. With this PR we have now aligned how deprecation works with HC.
https://graphql.github.io/graphql-spec/draft/#sec--deprecated
DeprecationReason
is now obsolete. In order to be more explicit I have introducedDeprecated
for the code-first variant.descriptor.Deprecated("reason")
ordescriptor.Deprecated()
can be used to deprecate a field or enum value.With code first we now are able to use
@deprecated
without any arguments.