-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto fix conflict (implicit-arrow-linebreak and max-len) #11408
Comments
Hi @jabacchetta , thanks for this issue. I can reproduce this bug. |
This doesn't seem like a bug to me. The autofixers for some rules can generally create linter problems for other rules. |
Can we change the autofixer to create parens and linebreaks like @jabacchetta mentioned? |
Of course I know each rule shouldn't concern other rules, but this is really confusing in UX. |
It seems like the user would sometimes want everything to be on the same line. Since the |
Any details? |
For example, in the Personally, I'm not sure this is worthwhile, but it would be one way to sometimes address the confusing UX. |
Relabeling as an "enhancement" because it's expected that autofixers for some rules can sometimes create linter problems for other rules. |
Unfortunately, it looks like there wasn't enough interest from the team Thanks for contributing to ESLint and we appreciate your understanding. |
Was looking for this tonight. C'mon eslint bot, show us and them sweet arrow functions some love. |
Tell us about your environment
5.3.0
10.10.0
6.4.1
What parser (default, Babel-ESLint, etc.) are you using?
babel-eslint
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
What did you expect to happen?
What actually happened? Please include the actual, raw output from ESLint.
Are you willing to submit a pull request to fix this bug?
Not in the near future, but would be willing to eventually.
The text was updated successfully, but these errors were encountered: