linter: fix codebase for same rule in different plugin/scopes

[Sysix]

Background

In the eslint world there are similiar rule (names) in different plugins. As an example:

• no-unused-vars and @typescript-eslint/no-unused-vars
• vitest/no-identical-title and jest/no-identical-title

Problems

Because oxlint support them only in one scope (vitest in jest and @typescript-eslint in eslint),
there are some problems.

Documentation

• fix(docs): detect typescript alias rules and mark them as supported #3779 (and some follow up)
• fix(tasks/lint_rules): sync vitest compatible rules with jest rules #6667

Implementation with config

• linter: no matching rules for some typescript rules #7233
• linter: jest and vitest compatible rules are reported as not supported #7240

Integration with eslint-plugin-oxlint

in this project we need to keep track for the configs and the new method buildFromOxlintConfigFile

• sync vitest compatible rules with jest rules eslint-plugin-oxlint#187
• fix: mark typescript rules, which extend eslint rule, as supported eslint-plugin-oxlint#165

Discussion

I want to have a simple way to parse the rules for all specific use cases.
In discord there is also a import/no-namespace upcoming rule wich conflicts with @typescript-eslint,
see here https://discord.com/channels/1079625926024900739/1080712072012238858/1304749400383291422
This problem crops up more often, the more plugins we are supporting.

[nrayburn-tech]

I agree that this is an issue and I would like to see it addressed somehow. As you mention, the more plugins that are supported the more often this is an issue. I expect it will continue to get worse, especially when custom plugins become available.

[Boshen]

It was an oversight to not allow identical names, let's treat it as a bug and fix accordingly.

[pumano]

Would love if it will be fixed, because typescript/no-namespace and import/no-namespace can be used too without changing name

[pumano]

Looks like #7082 related to that problem too.

@Sysix @nrayburn-tech how we can fix it?

[Sysix]

I do not know how the perfect solution looks like :)

My first guess is the modifiy the rules.rs:

• allow exporting a imported rule multiple times with different names
• renaming all declare_all_lint_rules rules with plugin scope
• add missing rules from same scope (vitest to jest, ts to eslint)

But this is too big of a problem for me, I do know the architecture of oxc.
Someone from the core team should look into this:)

[pumano]

@camchenry @camc314 could you help us with that solution or guide us, how we can do it?

[camc314]

thoughts on the following:
when using the cli, rules can either be enabled with their name
e.g no-non-null-assertions
OR their scoped name @ typescript/no-non-null-assertions

?

will try to look at this tomorrow