Open yvele opened 2 years ago
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:
--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:
+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.
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: