alwaysShowRuleFailuresAsWarnings doesn't change severity
See original GitHub issueI’m trying to migrate to this plugin from deprecated vscode-tslint
. My configuration is
{
"extends": "./tsconfig.base",
"plugins": [{
"name": "typescript-tslint-plugin",
"alwaysShowRuleFailuresAsWarnings": false
}]
}
But alwaysShowRuleFailuresAsWarnings
has no effect and errors are always displaying as warnings. vscode-tslint
works fine.
VSCode v1.30.0 TypeScript v3.1.6 (workspace) and v3.2.2 (vscode)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:6 (1 by maintainers)
Top Results From Across the Web
alwaysShowRuleFailuresAsWar...
alwaysShowRuleFailuresAsWarnings doesn't change severity #40 ... But alwaysShowRuleFailuresAsWarnings has no effect and errors are always ...
Read more >ESLint/TSLint - add severity where array is being used in ...
I'm trying to set the severity of the one-line rule to warning, but the array of checks does not seem to accept "severity":...
Read more >TSLint - Visual Studio Marketplace
alwaysShowRuleFailuresAsWarnings - Always show rule failures as warnings, ignoring the severity configuration in the tslint.json ...
Read more >Errors don't disappear after resolving
I re-tried the tslint.alwaysShowRuleFailuresAsWarnings setting just to be sure, and it does work for us – the severity immediately changes to ...
Read more >typescript-tslint-plugin - npm package
alwaysShowRuleFailuresAsWarnings - Always show rule failures as warnings, ignoring the severity configuration in the tslint.json configuration. Default is true ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’re experiencing the same issue. When we run lint via the CLI, we get errors/warnings as configured. In VS code they all appear as warnings. However, if I re-save the tsconfig file (even with no modifications), then after 15-20 seconds the plugin appears to honor the setting (the green squiggles change to red for errors). It seems like the plugin is listening for tsconfig changes and applying the setting, but sadly doesn’t appear to apply them correctly on initial load.
A side question, why is
alwaysShowRuleFailuresAsWarnings
defaulted to true?I’m encountering the same problem as what @craigsmitham describes