no-extra-parens options work inconsistently

[yeonjuan]

Tell us about your environment

• ESLint Version: v.6.8.0
• Node Version: v12.13.0
• npm Version: v6.12.0

What parser (default, Babel-ESLint, etc.) are you using?

default(espree)

Please show your full configuration:

Configuration

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

• The enforceForArrowConditionals: false option doesn't allow extra parentheses more than one pair. - demo

/* eslint no-extra-parens: ["error", "all", { "enforceForArrowConditionals": false }] */

const b = a => 1 ? 2 : 3;
const e = c => (1 ? 2 : 3);
const f = c => (((1 ? 2 : 3))); // Unnecessary parentheses expression.
const g = c => ((((1 ? 2 : 3)))); // Unnecessary parentheses expression.

• On the other hand, the other options allow extra parentheses without limit. - demo

/* eslint no-extra-parens: ["error", "all", {
	"conditionalAssign": false,
	"nestedBinaryExpressions": false,
        "ignoreJSX": "all",
        "enforceForSequenceExpressions": false,
        "enforceForNewInMemberExpressions": false
}] */

while ((((foo = bar())))) {}

x = a || (((((b && c)))));

const baz = ((((<div/>))));

(((a, b)));
((a, b));
(a, b);

var foo = (((new Bar()))).baz;
var foo = ((new Bar())).baz;
var foo = (new Bar()).baz;

What did you expect to happen?

I think the options should work consistently.
By the docs, the option enforceForArrowConditionals: false should allow all extra parentheses without limitation in matched cases with the option.

...
"enforceForArrowConditionals": false allows extra parentheses around ternary expressions which are the body of an arrow function
...

What actually happened? Please include the actual, raw output from ESLint.

Are you willing to submit a pull request to fix this bug?

Yes. If this issue is a bug. After #12697 merged.

[kaicataldo]

This seems like a bug to me. Thanks for reporting this 👍