Skip to content

Exclude rather than include lints #57337

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

Closed
donny-dont opened this issue May 27, 2016 · 3 comments
Closed

Exclude rather than include lints #57337

donny-dont opened this issue May 27, 2016 · 3 comments
Labels
devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. type-enhancement A request for a change that isn't a bug

Comments

@donny-dont
Copy link

It would be a lot nicer to have lints be opt out rather than opt in. I personally find myself on the update treadmill anytime a new lint is released.

Maybe something like

linter:
  exclude:
    - always_specify_types
@zoechi
Copy link
Contributor

zoechi commented May 27, 2016

I don't know if there is an issue that targets this better than #57153 but there was a discussion to introduce sets of rules like Dart style guide, Flutter style guide, ... and then to configure one or more such groups. When then new rules are added to a configured group it should be automatically applied.

@pq
Copy link
Member

pq commented May 27, 2016

Another related conversation over here: #25843.

As @zoechi says, some notion of rule set inheritance would really help here.

A bit more relevant to that in #26154 and this doc. Input welcome!

@pq pq added the type-enhancement A request for a change that isn't a bug label May 27, 2016
@bwilkerson
Copy link
Member

In general, we do not want lints to be opt-out because we want it to be possible to define contradictory lint rules and allow users to decide which rules to apply. Providing rule sets would solve most of the problems but allow lints to remain opt-in.

@devoncarew devoncarew added devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. labels Nov 18, 2024
@devoncarew devoncarew transferred this issue from dart-archive/linter Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devexp-linter Issues with the analyzer's support for the linter package legacy-area-analyzer Use area-devexp instead. type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

5 participants