Closed a-carvallo closed 3 years ago
Thanks for the PR!
Has this always been the case or was this a change to tslint? Do we need to handle both cases?
Actually I'm pretty sure its always been this way. I'll go ahead and merge this and we can add support for both cases if it causes any grief
Thank you, and yes I think it was always like that, I had a project with tslint 5.15.0 (so from 2 years ago) and it was already lowercase.
Published 2.1.1
In tslint rule severity is lowercase, so the comparison in the plugin would never be true, and we end up with only errors or only warnings (but not a mix) depending on the value of
options.warningsAsError
.