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

dart fix --linter specific_linter_here #49809

Closed
FMorschel opened this issue Aug 24, 2022 · 4 comments
Closed

dart fix --linter specific_linter_here #49809

FMorschel opened this issue Aug 24, 2022 · 4 comments

Comments

@FMorschel
Copy link
Contributor

FMorschel commented Aug 24, 2022

I have a really big project that I and my team are returning to work on. Since we left it we started actually using the analysis_options.yaml with our own configurations and not only the defaults.

When we run the dart fix --dry-run command, we receive a lot of information at once since there are a lot of linters active now. We wondered if the dart fix --dry-run could have a property like linter followed by a linter name where it would show all the solves just for that specific linter.

Maybe even have a count parameter where it would just name the linters and show how many warnings (not ignored cases) there are in the project. This would help us a lot to fix our project and keep it with the same standards our other projects have.

@FMorschel FMorschel closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2022
@FMorschel FMorschel changed the title Create an issue dart fix --linter _specific_linter_here_ Aug 24, 2022
@FMorschel FMorschel changed the title dart fix --linter _specific_linter_here_ dart fix --linter specific_linter_here Aug 24, 2022
@FMorschel
Copy link
Contributor Author

Closed it by accident.

@bwilkerson
Copy link
Member

@pq

@pq
Copy link
Member

pq commented Aug 24, 2022

We're actually working on something that should do just this trick. With the upcoming --code option you'll be able to specify one of more diagnostic codes to limit fixes to. See: #47219

@pq
Copy link
Member

pq commented Aug 24, 2022

If there's anything in that feature request that doesn't cover your use case, please chime in there. Thanks!

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