oxc-project
oxc
BlogDocsChangelog

fix(linter): don't report unknown rules as unused directives (#11983)

#14818
Comparing
taearls:11983/fix/custom-lint-rules-reported-unused
(
74a721b
) with
main
(
e064079
)
CodSpeed Performance Gauge
0%
Untouched
4
Skipped
33

Benchmarks

Skipped (33)

Passed

linter[RadixUIAdoptionSection.jsx]
tasks/benchmark/benches/linter.rs::linter::bench_linter
CodSpeed Performance Gauge
0%
708.4 µs706.5 µs
linter[cal.com.tsx]
tasks/benchmark/benches/linter.rs::linter::bench_linter
CodSpeed Performance Gauge
0%
465.9 ms466 ms
linter[react.development.js]
tasks/benchmark/benches/linter.rs::linter::bench_linter
CodSpeed Performance Gauge
0%
18.7 ms18.7 ms
linter[binder.ts]
tasks/benchmark/benches/linter.rs::linter::bench_linter
CodSpeed Performance Gauge
0%
46.7 ms46.8 ms

Commits

Click on a commit to change the comparison range
Base
main
e064079
+0.03%
fix(linter): recognize @typescript-eslint/* format for typescript plugin rules Fixes regression where `@typescript-eslint/no-floating-promises` and other typescript plugin rules were incorrectly classified as "unknown" in disable directives, preventing them from being reported as unused. The `is_known_rule()` function was caching typescript rules using the internal format `@typescript/rule-name`, but ESLint users write `@typescript-eslint/rule-name` in their disable comments (following the official @typescript-eslint plugin convention). This commit adds special handling to recognize both formats, similar to the existing jest→vitest and eslint→typescript remapping logic. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
74a721b
2 months ago
by taearls
© 2026 CodSpeed Technology
Home Terms Privacy Docs