you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 3 years ago (2 children)

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

  • source
  • hideshow 4 child comments
  • [–] 9 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 3 years ago* (1 child)

    Ahh the solution is simple, in VS Code add these lines to your general config

        "workbench.colorCustomizations": {
            "editorError.foreground": "#00000000",
            "editorWarning.foreground": "#00000000",
            "editorInfo.foreground": "#00000000", 
        },
    

    Then get the error lens extension, it's so much more pleasant. Visual example

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 years ago

    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.

  • source
  • parent