Higher order functions and the arrow-parens rule

The arrow-parens rule requiring parentheses for blocks and no parentheses for one-liners takes no account of higher order functions.

I find it downright bizarre that I should be required to write code like the following:

return next => (action) => {
  // etc
};

I don’t know whether this is a config issue or an eslint issue.

[felixsanz]

Here is an example that doesn’t make any sense:

    ${headTags.scripts.map((script) => {
      if (script.src) return `<script src="${script.src}"></script>`
      return `<script>${script.content}</script>`
    }).join('\n')}

    ${headTags.links.map(link => (
      `<link ${Object.entries(link).map(([prop, value]) => (`${prop}="${value}"`)).join(' ')}>`
    )).join('\n')}

Where is the consistency between (script) and link? Looks so bad!

It should be always or never (i’m talking about single argument in function signature)

[TigerC10]

Just now found this issue myself, taking a look at:

    // require parens in arrow function arguments
    // http://eslint.org/docs/rules/arrow-parens
    'arrow-parens': ['error', 'as-needed', {
      requireForBlockBody: true,
    }],

https://github.com/airbnb/javascript/blob/7e865a4e8ab5e26062fcdc9437166c6e1c269599/packages/eslint-config-airbnb-base/rules/es6.js#L25

Yeah, I gotta admit I’m a bit bewildered by requireForBlockBody being true. But I guess I fall into the camp where arrow-parens are always required. Helps me visually associate that arg to the arrow function rather than to the wrapping function. 1 char diff between arrow function and assignment is not sufficient for my tastes.

Thank goodness for overrides. 🙄