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
--comment-descriptions
I switched from graphql-schema-linter v2.0.2 to v3.0.1
And now I have a lot of types-have-descriptions and fields-have-descriptions reports.
types-have-descriptions
fields-have-descriptions
This should be OK using --comment-descriptions:
# Foo description. type Foo { # Unique identifier. id: ID! }
Everything was OK using v2.0.2
Note that I'm building a schema for AWS AppSync and I need the old way of defining descriptions:
The text was updated successfully, but these errors were encountered:
+1
I'm using AWS AppSync - Although it's annoying why AWS still doesn't support proper descriptions, would be amazing if --comment-descriptions worked.
Sorry, something went wrong.
No branches or pull requests
I switched from graphql-schema-linter v2.0.2 to v3.0.1
And now I have a lot of
types-have-descriptions
andfields-have-descriptions
reports.This should be OK using
--comment-descriptions
:Everything was OK using v2.0.2
Note that I'm building a schema for AWS AppSync and I need the old way of defining descriptions:
The text was updated successfully, but these errors were encountered: