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

Cli option --fail-on-all-warnings #118

Open
dawedawe opened this issue Oct 12, 2023 · 1 comment
Open

Cli option --fail-on-all-warnings #118

dawedawe opened this issue Oct 12, 2023 · 1 comment

Comments

@dawedawe
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently, to fail on a warning, you have to list all the analyzer codes you want to fail on. If you are using many analyzers and you want to fail on all of them, that can be cumbersome.

Describe the solution you'd like
Provide a --fail-on-all-warnings Cli option.

Describe alternatives you've considered
Support globbing of analyzer codes.

Additional context
As always, I just raise this issue to keep track of it.

@baronfel
Copy link
Collaborator

Consider a syntax like NoWarn in the compiler to allow setting diagnostic levels on a per message basis, as well as the more general 'treatwarningsaserror' mechanism: https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/errors-warnings

I think it would be good for the analyzer SDK to onboard to these mechanisms because that's how they would be handled/integrated in the 'final' analyzer setup, when they're part of the compiler.

1eyewonder added a commit to 1eyewonder/FSharp.Analyzers.SDK that referenced this issue Oct 21, 2023
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