[no-confusing-arrow]: new line, and multiple parameters should be allowed

Tell us about your environment

• ESLint Version: 4.1.1
• Node Version: 8.1.3
• npm Version: 5.0.3

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

Please show your full configuration:

"no-confusing-arrow": [2, {"allowParens": true}],

What did you do? Please include the actual source code causing the issue.

// case 1: arrow function body in new line
imageURLToBlob(imageURL, (blob) =>
     blob ? resolve(blob) : reject());

// case 2: arrow function with multiple parameters
var fn = (exists, localURL) => exists ? resolve(localURL) : reject();

What did you expect to happen? A new line should make the intended arrow function use case of ‘=>’ obvious. Or there should be an option to accept this as not confusing.

Multiple parameters again should make an operator ‘=>’ unambiguously treated as an arrow function.

What actually happened? Please include the actual, raw output from ESLint. Both cases report arrow functions can be confused with mathematical operators.

[not-an-aardvark]

I think the allowParens option is intended to refer to whether the body of the function is parenthesized, not the parameters.

That said, I’ve always been a bit unclear on what makes the arrow “confusing”.

[nzakas]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to be implemented after 90 days tend to never be implemented, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.