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).
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.
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.
