-
Notifications
You must be signed in to change notification settings - Fork 887
4.0: 'no-unused-variable is deprecated....' message when using "extends": "tslint:recommended" #1748
Comments
If we need to have this warning, can we at least show it ONLY, when rule is enabled. It is pretty inconvenient to copy whole config file to get rid of it. Never mind. It won't work as everybody will get recommended config, where it is disabled. |
The notice should be suppressed, once the rule is actively disabled in the config: {
"extends": "tslint:latest",
"rules": {
"no-unused-variable": false
}
} Right now, the notice still appears (and doesn't fair well with some JetBrains-IDEs). |
@Ungolianth not for me: as long as the rule is mentioned (including as Edit: I've read your post as a 'I think that works' vs 'I think this is how it should work': in the latter case, I wholeheartedly agree (and it would be helpful to include a hint in the warning message itself or at least in the blog post) |
@locobert yes, it was meant to be "It should work like this, but right now it does not". Modifying |
:) Yes, modifying |
sorry about that, v4.0.1 should have the fix |
Did you update your tslint package? All JetBrains IDEs show this behaviour (I use PHPStorm and IntelliJ), as they cannot map the deprecated message to a specific file. Removing the |
In fact, i prefer to turn on this rule because it can't be disabled for some code with common tag, which the tsc can't achieve for now. |
@e-cloud what do you mean by "common tag" here? With |
sorry, typo. I mean use tslint comment flag to disable something. |
The problem with using the flag in |
When using TSLint 4.0 with a rule set that
"extends": "tslint:recommended"
, the following deprecation message is always shownRemoving the rule from
node_modules/tslint/lib/configs/recommended.js
(where it is set tofalse
) fixes itThe text was updated successfully, but these errors were encountered: