Skip to content
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

lint-disable-line doesn't work when a field has a description #289

Open
vikstrous2 opened this issue Jun 25, 2021 · 1 comment
Open

lint-disable-line doesn't work when a field has a description #289

vikstrous2 opened this issue Jun 25, 2021 · 1 comment

Comments

@vikstrous2
Copy link

linter version: 2.0.1

$ graphql-schema-linter example.graphql
<redacted>/example.graphql
1:1 A `PageInfo` object type is required as per the Relay spec.  relay-page-info-spec
4:1 The object type `Query` is missing a description.            types-have-descriptions
5:3 The field `Query.A` is not camel cased.                      fields-are-camel-cased
5:3 The field `Query.A` is missing a description.                fields-have-descriptions
7:1 The enum type `A` is missing a description.                  types-have-descriptions
8:3 The enum value `A.Wrong` should be uppercase.                enum-values-all-caps

✖ 1 error detected
$ cat example.graphql
schema {
  query: Query
}
type Query {
  A: String
}
enum A {
  """
  description
  """
  Wrong # lint-disable-line enum-values-all-caps
}

I expected the last linter violation to be ignored.

@mcwoodle
Copy link

Encountered the same issue. Only workaround was to disable multiple lines like:

enum A {
  # lint-disable enum-values-all-caps
  """
  description
  """
  Wrong 
  # lint-disable enum-values-all-caps
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants