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
fixes#7009
allows rules to be replaced properly when the `rules_for_override` array is empty (e.g., if you initially disable all rules, then configure them) by checking the `all_rules` array if the first `find` call fails
- closes#6988
we now return an error exit code when there are unmatched rules. previously, we would print an error to stderr and continue running. however, this masked errors in some tests that actually had unmatched rules in them. these test cases now trigger a panic (in tests only, not at runtime), and help ensure that we are reporting an error message to the user for unknown rules, which we did not have any tests cases for before.
- fixes#7025
this also fixes#7025, where we were reporting rules as unmatched simply because they had been disabled prior to being configured. similar to #7009.
What version of Oxlint are you using?
0.10.3
What command did you run?
oxlint -c .oxlint.json
What does your
.oxlint.json
config file look like?and
What happened?
First config output:
Second config output:
The text was updated successfully, but these errors were encountered: