Auto fix conflict (implicit-arrow-linebreak and max-len)

Tell us about your environment

• ESLint Version: 5.3.0
• Node Version: 10.10.0
• npm Version: 6.4.1

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

Please show your full configuration:

Configuration

"eslintConfig": {
  "parser": "babel-eslint",
  "rules": {
    "max-len": ["error", 100],
    "implicit-arrow-linebreak": ["error", "beside"]
  }
}

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

const someIncrediblyRidiculousSuperLongFnName = (foo, bar) =>
  someOtherIncrediblyRidiculousSuperLongFnName(foo, bar);

eslint --fix

What did you expect to happen?

const someIncrediblyRidiculousSuperLongFnName = (foo, bar) => (
  someOtherIncrediblyRidiculousSuperLongFnName(foo, bar)
);

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

// FIXME: Fixed implicit-arrow-linebreak, but broke max-len
const someIncrediblyRidiculousSuperLongFnName = (foo, bar) => someOtherIncrediblyRidiculousSuperLongFnName(foo, bar);

Are you willing to submit a pull request to fix this bug? Not in the near future, but would be willing to eventually.

[eslint-deprecated[bot]]

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 reach accepted status after 21 days tend to never be accepted, 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.

Thanks for contributing to ESLint and we appreciate your understanding.

[DZuz14]

Was looking for this tonight. C’mon eslint bot, show us and them sweet arrow functions some love.