arrow-body-style: [2, "as-needed"] should ignore function bodies that return another block/function

Granted the below example could be achieved a number of different ways to produce the same results, it’s a use case that I think others might find useful if handled in the way I’m expecting.

The following code will fail ESLint v1.9.0 with arrow-body-style: [2, "as-needed"]:

function foo() {
  return (bar, baz) => { // Unexpected block statement surrounding arrow body. (arrow-body-style)
    return qux => {
      console.log(bar);
      console.log(baz);
      console.log(qux);
    };
  };
}

foo()("bar", "baz")("qux");

I expect the above (contrived currying example) to pass since, as far as I know, a block is required here.

[bartekus]

I’ll second @mattkrick on that, and provide practical example in form of Login.js component:

import React, { PropTypes } from 'react';

const Login = (props) => {
  return <a onClick={props.onClick}>Login</a>;
};

Login.propTypes = {
  onClick: PropTypes.func.isRequired,
};

export default Login;

There is definitely need for such pattern and that need will only increase as we further push the envelope of possibilities that react&redux for example allow.

Please reconsider you position on this.

[mysticatea]

@elgubenis It’s arrow-body-style’s warning. The arrow functions of your code have only a return statement in the body, so you can rewrite them with () => foo style.