Update: Fix handling of chained new expressions in new-parens #12303
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.
What is the purpose of this pull request? (put an "X" next to item)
[X] Bug fix
This bug fix can produce more errors by the
new-parens
rule in some cases. Also fixes wrong autofix in some other cases.Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
default
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue.
Demo link 1
Demo link 2
What did you expect to happen?
1 error and the following autofix for the first example:
1 error and the following autofix for the second example:
What actually happened? Please include the actual, raw output from ESLint.
0 errors in the first example:
2 errors and a bit invalid autofix in the second example:
What changes did you make? (Give an overview)
Check that the parens are not a part of the child node.
Is there anything you'd like reviewers to focus on?