This repository has been archived by the owner on Mar 29, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Create a global override of issues severity. #19
Labels
Comments
Having a build property for this is a good idea. It would be better to have it as something like |
I agree it'd be better to have a parameter for severity. |
:) Please do! |
As of 0.4.X, the error output format is:
|
JoshuaKGoldberg
pushed a commit
that referenced
this issue
Jul 2, 2016
Optional MSBuild error severity override, as `"error"` or `"warning"`. Fixes #19.
JoshuaKGoldberg
pushed a commit
that referenced
this issue
Jul 2, 2016
* Added an optional `TSLintErrorSeverity` flag Optional MSBuild error severity override, as `"error"` or `"warning"`. Fixes #19. * Fixed README.md ordering for error severity * Moved the "X errors found" message above errors Now that error printing is a source of errors (albeit very unlikely) it makes sense to have the summary first.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Right now when using TSLint.MSBuild, all issues are reported as errors. I understand this is a tslint problem (palantir/tslint#345) that will be fixed at some point, but right now this issue prevents me from using tslint.
Most of the issues raised by other linters/analysers in my projects are warnings, and I do not want errors to show up for spacing issues.
There might be another way of doing this I am not aware of, if not, would you consider adding a msbuild property (something like TSLintTreatErrorsAsWarnings) for this purpose ?
Cheers
The text was updated successfully, but these errors were encountered: