We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
The @deprecated annotation I can see is now supported under the draft on the spec https://spec.graphql.org/draft/#sec--deprecated. But not for the current released one https://spec.graphql.org/October2021/#sec--deprecated.
@deprecated
I'm using the https://www.npmjs.com/package/graphql-schema-linter version 3.0.1 and graphql version 15.6.1 and this appears to be happy with deprecating the fields on input types.
I can take a look at adding support for this but want to know if this would be accepted? or do we keep to the October2021 version?
Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
The
@deprecated
annotation I can see is now supported under the draft on the spec https://spec.graphql.org/draft/#sec--deprecated. But not for the current released one https://spec.graphql.org/October2021/#sec--deprecated.I'm using the https://www.npmjs.com/package/graphql-schema-linter version 3.0.1 and graphql version 15.6.1 and this appears to be happy with deprecating the fields on input types.
I can take a look at adding support for this but want to know if this would be accepted? or do we keep to the October2021 version?
Thanks
The text was updated successfully, but these errors were encountered: