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

Support ignoring a rule for all types. #274

Open
tmc opened this issue Jan 10, 2021 · 3 comments
Open

Support ignoring a rule for all types. #274

tmc opened this issue Jan 10, 2021 · 3 comments

Comments

@tmc
Copy link

tmc commented Jan 10, 2021

No description provided.

@cjoudrey
Copy link
Owner

Hey @tmc, thanks for opening this issue.

Can you provide a bit more clarity on the issue you're reporting?

Thanks!

@scags9876
Copy link

I am curious about this as well. If i want to completely ignore a rule for all fields and all types, is that possible?
with the following config file:

{
  "ignore": {
  	"types-have-descriptions": ["Movie"], 
  	"enum-values-have-descriptions": ["Genre"]
  },
}

only disables these rules for Movie types and Genre enums. I want to just not see these rule active for any type or field. If i add a new enum and don't add descriptions for the values, schema linting should pass without me updating my schema linter config.

@cjoudrey
Copy link
Owner

cjoudrey commented May 5, 2021

If you want to completely disable enum-values-have-descriptions, you can configure what rules to be run using "rules": ["..."] (or --rules ...). For example: https://github.com/cjoudrey/graphql-schema-linter#in-packagejson.

This is an opt-in list though and not an ignore list.

Let me know if I misunderstood your request.

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

3 participants