oxc-project
oxc
BlogDocsChangelog

fix(linter/no-useless-undefined): correctly respect `checkArguments` option

#14369Merged
Comparing
c/10-06-fix_linter_no-useless-undefined_respect_checkarguments_option
(
e605222
) with
main
(
f5c6acc
)
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%
1.6 ms1.6 ms
linter[cal.com.tsx]
tasks/benchmark/benches/linter.rs::linter::bench_linter
CodSpeed Performance Gauge
0%
731.4 ms731.3 ms
linter[binder.ts]
tasks/benchmark/benches/linter.rs::linter::bench_linter
CodSpeed Performance Gauge
0%
89 ms89 ms
linter[react.development.js]
tasks/benchmark/benches/linter.rs::linter::bench_linter
CodSpeed Performance Gauge
0%
33.1 ms33.1 ms

Commits

Click on a commit to change the comparison range
Base
main
f5c6acc
0%
fix(linter/no-useless-undefined): correctly respect `checkArguments` option (#14369) The rule was not correctly parsing the configuration from .oxlintrc.json. When rules are configured with options like: { "rules": { "unicorn/no-useless-undefined": ["error", { "checkArguments": false }] } } The config system passes the options as an array containing all elements after the severity: [{ "checkArguments": false }] The from_configuration method was trying to access properties directly on the array instead of getting the first element. This fix uses value.get(0) to extract the options object from the array, matching the pattern used by all other rules in the codebase. Also updated the test configuration helpers to use the correct array format, consistent with other rules' tests. Fixes #14368
e605222
1 month ago
by camc314
© 2025 CodSpeed Technology
Home Terms Privacy Docs