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