You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The linter only works when the plugins property is set in the root of the config file, when the plugins property is set in the overrides property, the linter does not work.
I had look into this a little bit. I think there is a specification issue here that we need to think about. The problem essentially boils down to the order in which rules are enabled causes the difference in behavior.
When enabling plugins at the top-level, it allows those rules to be accessible as part of the base rule set, which then factors into which rules are enabled by categories. But if the plugins are enabled as part of an override, it can't factor into the base rule set, since that happens too late and we don't recalculate the base rules at that point.
If we want categories to apply to overrides as well, then we probably need to store what categories are enabled in the ConfigStore, not just compute the base rule set once at the beginning.
What version of Oxlint are you using?
0.15.13
What command did you run?
yarn oxlint -c .oxlintrc.json index.test.ts
What does your
.oxlintrc.json
config file look like?What happened?
The linter only works when the
plugins
property is set in the root of the config file, when theplugins
property is set in theoverrides
property, the linter does not work.This is the config file that works:
But this one doesn't work:
Screen.Recording.2025-03-10.at.11.02.11.mov
The text was updated successfully, but these errors were encountered: