Hacker News new | ask | show | jobs
by bbu 231 days ago
I’ve heard this argument before but I don’t get it. It’s trivial to setup your code editor to format on save. Why do people not do that but rather complain about files linter checks on CI?
2 comments

I don't think they were talking about formatting issues, since these tend to not change the behaviour of the code (outside of Python) so that you can't use the tests before addressing the linter issues.
Biome can fail the lint process if there’s an extra new line. Or you shortened a line that it thinks shouldn’t be wrapped anymore, or you added an argument to a line that it thinks should. I hates it.
It’s trivial to set up my code editor to save to the format of six different GitHub repos? Do tell.

One of them uses tabs. Fucking Richard.

Your code editor should respect the .editorconfig of the repo you are editing, so yeah, trivial.
Bold of you to assume aggravating projects have an editorconfig. (Checked, the worst doesn't)
Only one does as it turns out.