`no-confusing-arrow` flags conditionals inside parentheses.

ESLint Version: 2.1.0

This is a pattern I use frequently in JavaScript code:

const renderItem = item => (isSeparator(item)
  ? React.createElement(Separator)
  : React.createElement(MenuItem, item)
)

Note that the conditionals are inside parentheses. In this case, the meaning is not ambiguous. You can’t interpret a => (1 ? 2 : 3) as (a >= 1) ? 2 : 3.

Test Case

/* eslint no-confusing-arrow: 2 */
var x = a => (1 ? 2 : 3)

Expected Result

No lint errors.

Actual Result

Arrow function used ambiguously with a conditional expression. (no-confusing-arrow)

[shinzui]

Is allowParens set to true supposed to work with no-extra-parens. It’s now triggering “Gratuitous parentheses around expression. (no-extra-parens)”.

[dtinth]

Would love to work on it, but have been quite busy, so I am not sure whether I’ll have time to do it.

@nzakas @jeremejevs @gilbarbara What do you think about @alberto’s case?

Does var x = a => (true ? 2 : 3) look confusing?

For me, I think it’s pretty clear that it’s a function that returns some value, because I get used to seeing this: => (.