fix: validate options when comment with just severity enables rule #18133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[x] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
Tell us about your environment (
npx eslint --env-info
):What parser are you using (place an "X" next to just one item)?
[x]
Default (Espree)
[ ]
@typescript-eslint/parser
[ ]
@babel/eslint-parser
[ ]
vue-eslint-parser
[ ]
@angular-eslint/template-parser
[ ]
Other
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue.
/* eslint accessor-pairs: "error" */
What did you expect to happen?
A lint error about invalid configuration for rule
accessor-pairs
, because the final configuration for this rule is["error", "foo"]
(severity from the inline config comment, options from the config file), which isn't valid.What actually happened? Please include the actual, raw output from ESLint.
No errors.
This happens because config arrays (both eslintrc and flat) don't validate options when rule is set to
"off"
in the configuration, which is intended behavior, but when that rule is later enabled by a comment and inherits options from the configurations, those options should be validated.What changes did you make? (Give an overview)
This scenario wasn't covered in #17945. Now I moved the logic that calculates options for a configuration comment to an earlier point so that the validation gets the final options.
Is there anything you'd like reviewers to focus on?