this post was submitted on 30 Jun 2023
321 points (96.5% liked)
Programming
17366 readers
190 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This would bite me in the ass because I often ignore these kinds of warnings in VSCode (SFDX for VSC is kinda crap, warns you about nonissues, and often doesn't correctly identify the problem).
Confusable characters get a little yellow box which is different from the squiggly underlines most linters and stuff use which at least makes it a bit more recogniseable.
Personally I can't stand having underlines all over my code, so I'll usually just "fix" the non-issue if possible, or otherwise just disable whatever the warning is entirely.
Ahh the solution is simple, in VS Code add these lines to your general config
Then get the error lens extension, it's so much more pleasant. Visual example
I love that look, ugh. The inline errors are much more visually appealing vs the usual squiggly underline
I might need to look at vscodium since I'm not too keen on having more microsoft telemetry on my desktop. Been using Atom for personal projects thus far.
Maybe have a look into Gremlins Tracker