We added ESLint in an effort to help us prevent errors, enforce a
consistent coding style, and hopefully have readable code.
>From my experience so far (bgrins will agree since we were just discussing
this on a bug), this rule is frustrating more often than not, doesn't
prevent any kind of errors, and doesn't help write readable code.
In fact, we've had to add a number of regex to the configuration so it
ignores things like long urls, require and other loader statements.
The problem when removing ESLint errors from an entire file and even an
entire directory is that you end up having to break lines that are just a
little longer than 80 characters for no other reasons than to please
ESLint. The is no really good option available to you when it comes to
choosing how to wrap a long line, and we don't have a consistent style for
doing it, nor another ESLint rule that enforces it.
I've made a poll some time ago on twitter:
https://twitter.com/patrickbrosset/status/703688265849819136
>From what I learned, most people don't really care.
So, please let me know if you think we should just disable the rule
altogether.
Let's vote in this thread:
- Let's disable the rule and try and stick to 80 but allow to go over if
need be: +1
- Let's keep the rule and continue wrapping lines:
Patrick