Open cjoudrey opened 4 years ago
When specifying an invalid rule in an inline configuration, graphql-schema-linter should let the user know.
graphql-schema-linter
For example, this should raise an error:
# lint-disable some-invalid-rule type Query { field: String }
Perhaps the process could terminate with an error like:
The inline configuration on line 1 of `filename.graphql` references a non-existing rule: some-invalid-rule
Similarly, we should gracefully handle when an inline configuration is specified without any rules.
This currently crashes:
# lint-disable type Query { field: String }
We could either (1) make it raise an error like above or (2) support this as a feature and make it disable all rules.
/cc @mshwery in case you're bored 😄
When specifying an invalid rule in an inline configuration,
graphql-schema-linter
should let the user know.For example, this should raise an error:
Perhaps the process could terminate with an error like:
Similarly, we should gracefully handle when an inline configuration is specified without any rules.
This currently crashes:
We could either (1) make it raise an error like above or (2) support this as a feature and make it disable all rules.
/cc @mshwery in case you're bored 😄