Config schemas are enforced for disabled rules #7690
Labels
accepted
There is consensus among the team that this change meets the criteria for inclusion
archived due to age
This issue has been archived; please open a new issue for any further discussion
bug
ESLint is working incorrectly
core
Relates to ESLint's core APIs and features
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
default
Please show your full configuration:
(n/a)
What did you do? Please include the actual source code causing the issue.
I created a rule with a required schema, like this:
I ran the rule on some code in
foo.js
with three different sets of options:What did you expect to happen?
In Case 1, I expected ESLint to run to completion without reporting an error, because a valid schema was provided.
In Case 2, I expected ESLint to report a schema error, because an invalid schema was provided (it was missing an option).
In Case 3, I expected ESLint to run to completion without reporting an error. The rule is disabled, so I shouldn't have to provide a schema while disabling it (e.g.
example-rule: [off, 4]
)What actually happened? Please include the actual, raw output from ESLint.
ESLint worked as expected in Case 1 and Case 2, but it reported a schema error in case 3.
The text was updated successfully, but these errors were encountered: