> You can enforce line length with either prettier or a linter and both can auto fix the issue.
It's not about whether it's automatic or not, it's about the code being worse (that is: harder to read). Breaking lines because it's 1 character over some arbitrary limit is almost always bad, whether it's automatic or manual.
Re:It Takes 6 Days to Change 1 Line of Code
by sanderjd on Sunday July 16, 2023 @02:01PM
(#36749829)
A human ever thinking about where to break a line is bad. Let the computers do that, in one standard way for a project, and never think or talk about it again. The amount of time people have wasted on trivia like this over the decades is astronomical. It doesn't matter what the answer is, pick one, make it automatic, and move on.
Re:It Takes 6 Days to Change 1 Line of Code
by morelisp on Sunday July 16, 2023 @03:59PM
(#36750850)
Both things are true. It's worth arguing about so infrequently it's never worth thinking about whether it's worth arguing about, let alone argue about; but automated tools still make decisions far worse than any human would make sometimes.
Yeah I'm always delighted to use clang-format rather than worry about where I should put the brackets.
Code style is the epitome of bikeshedding. Anything consistent is fine, and using a tool to automate that is a huge productivity win.
Because of this things like [`eslint-config-prettier`](https://github.com/prettier/eslint-config-prettier) exist to ensure conflicting eslint formatting rules are disabled if they can be handled by prettier.