fix(linter): use aliases when parsing cli rules

[lilnasy]

• Fixes linter: --allow CLI flag does not properly map alt plugin names #14906

What went wrong

• parse_rule_key has the logic for aliasing, and it is called by OxlintRules, but only during deserialization.
• CliRunner, via ConfigStoreBuilder, instantiates OxlintRules directly. No post processing, aliasing doesn't take place.

Fix

• Aliasing logic in parse_rule_key is split off as unalias_plugin_name.
• unalias_plugin_name is now called by ConfigStoreBuilder.
• LintFilterKind::parse seemed like a better place at first, but lifetimes required cloning.

[Copilot]

Pull Request Overview

This PR fixes a bug where plugin name aliases (e.g., react-hooks → react) were not being applied when rules were specified via CLI arguments. The fix extracts the aliasing logic into a separate function and ensures it's called when processing CLI rule filters.

Key Changes:

• Extracted unalias_plugin_name function from parse_rule_key to make aliasing logic reusable
• Applied aliasing in ConfigStoreBuilder for both rule enabling and disabling operations
• Added comprehensive test coverage for CLI rule aliasing behavior

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
crates/oxc_linter/src/config/rules.rs	Extracted aliasing logic into new unalias_plugin_name function
crates/oxc_linter/src/config/config_builder.rs	Applied aliasing when processing CLI rule filters and added test coverage

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codspeed-hq]

CodSpeed Performance Report

Merging #14912 will not alter performance

_{Comparing lilnasy:fix/14906 (94972fd) with main (7060863)¹}

Summary

✅ 4 untouched
⏩ 33 skipped²

Footnotes

1. No successful run was found on main (b607793) during the generation of this report, so 7060863 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 33 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[camc314]

Thank you!

[graphite-app]

Merge activity

• Oct 23, 9:36 AM UTC: @lilnasy we removed the merge queue label because we could not find a Graphite account associated with your GitHub profile.

You must have a Graphite account in order to use the merge queue. Create an account and try again using this link