linter: rule fixer improvements #4179
Labels
A-linter
Area - Linter
C-enhancement
Category - New feature or request
good first issue
Experience Level - Good for newcomers
I've been adding and repairing fixers to a lot of rules, but my ad-hoc approach
is not sustainable. This issue is a call for assistance, and tracks fixer
progress for each rule.
Prerequisites
--fix-dangerously
flag #4211--fix
oxlint-ecosystem-ci#19Rules
For rules with an existing fixer:
diagnostic_with_fix
), ensure that there areno cases where the fixer could create a syntax error or semantically different
code.
differently different code in others, use
diagnostic_with_fix_dangerous
.update this table. If no changes are needed, leave a comment here and we'll
also update the table.
For rules without a fixer:
a fixer implementation that links to this issue.
a maintainer will update the table.
Legend
Correctness (159):
Code that is outright wrong or useless.
Perf (6):
Code that can be written to run faster.
Restriction (49):
Lints which prevent the use of language and library features. Must not be enabled as a whole, should be considered on a case-by-case basis before enabling.
Suspicious (14):
code that is most likely wrong or useless.
Pedantic (66):
Lints which are rather strict or have occasional false positives.
Style (80):
Code that should be written in a more idiomatic way.
Nursery (9):
New lints that are still under development.
The text was updated successfully, but these errors were encountered: