[tremere]

What bothers me most about VScode is that linters and other annotating plugins will underline and box text and make it really hard to read. It's not graceful the way error highlighting was in Eclipse and Visual Studio and it makes me miss the old tools. It's really really ugly, especially the box. Everyone says "just get a plug-in like ErrorLens" but I would rather just have a de-lint button. I honestly turn off the linter nowadays and run it manually in the shell (fortunately VSCode has a shell built in).

[rcme]

Why use a linter if your code has so many errors?

[tremere]

Lol. To fix them? They are not errors as much as warnings that are still helpful and I would like to keep. I just don't want the ugly box and underline which makes text unreadable.

Even when the error involves balancing parentheses the ugly box gets in the way. VScode has a neat trick of color coding parens so that balancing them is a bit more efficient, but with a tight box around your text and a squiggly underline it's just an unreadable mess.

Honestly turning off the linter has been the most helpful. Now I avoid forgetting semicolons and not balancing parens simply because of how painful using the linter is, that I would rather avoid it altogether. But it didn't have to be this way. They could have just not made error highlighting so terrible. It's garbage and everyone knows it is, anyone who tells me errors don't look absurd on VSCode is someone I stop taking seriously. It would be as if your teacher used a thick sharpie to black out what she thought were your mistakes in your essay, rendering you unable to even figure out what mistake you made in the first place.

[specialist]

The errors are in other people's code.

My own code, FWIW, is flawless. Natch.

[rcme]

Why are you running linters on other peoples' code?

[bjornasm]

Where did he say he had a lot of errors?

[rcme]

Presumably the readability issues only occur when there is a lint error.

[criley2]

I know people hate them but lint as a pre-commit hook is nice.

[lelandfe]

I turn them off. I commit early and often, and hooks just get in the way.

[smcleod]

Local hooks should be fast. I do that too if they take more than 5-10 seconds and it's not mission critical software.

[12345hn6789]

Early and often doesn't change code standards.

[lelandfe]

It sure does. The repository's standards don't matter one whit until I'm ready to submit my code.

I squash, amend, and delete history with aplomb as I develop. I simply do not need to be informed of adherence to code standards during that.

[mooooooooooooo]

You can always bypass the hook. Better to enforce standards and make exceptions when necessary.

[SamuelAdams]

You can change a setting to have VS Code auto-lint on file save. It will auto-fix as much as it can, anything that requires decisions will still need to be manually fixed.

https://stackoverflow.com/a/68016089