Don't require to specify deprecated rules
See original GitHub issueCurrently the command eslint-find-rules -u
ends with an error if you don’t specify deprecated rules. Ideally that wouldn’t be required; currently I just put them in a separate section and disable but that means my config will be broken as soon as those rules are removed which doesn’t seem necessary.
I’m not sure if ESLint returns enough data to make it possible; if not we could make it happen upstream first.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:14 (4 by maintainers)
Top Results From Across the Web
deprecated rule
A deprecated rule is a rule that is no longer supported. Where possible, migrate or upgrade these items to an appropriate alternative.
Read more >Warn on deprecated rules · Issue #7443 · eslint/eslint
The proposal in option A is to use warnings, which will not break CI builds. And we know formatters know how to handle...
Read more >Replace deprecated `only/except` with `rules` from ... - GitLab
Problem. The only/except keyword was deprecated in 13.0 however we still provide examples on how to use it on our documentation, ...
Read more >Working with Rules (Deprecated)
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Replace Deprecated Rules with New Rules - TechDocs
Sample Use Case. Deprecated Rule. Deprecated Rule Result ; User does not exist in the CA Risk Authentication database. USERKNOWN. No ; DeviceID ......
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 FreeTop 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
Top GitHub Comments
I’ve reported an issue upstream that would help for this & similar use cases: https://github.com/eslint/eslint/issues/7021 (and that would expose a proper API instead of having to hack into the internal ESLint package structure).
I would be happy to accept that PR on eslint-plugin-react. eslint-plugin-import has some deprecated rules as well, iirc.