Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Updated VSCode Warning Colors Do Not Match

See original GitHub issue

In VSCode update 1.36.1, a color was chosen for list.warningForeground and editorWarning.foreground - a golden yellow color. Since OneDarkPro does not specify colors for those fields, the same golden yellow shows up by default in the editor, breaking the consistency of the OneDarkPro theme.

See here for the change.

I’ve been using

"workbench.colorCustomizations": {
        "list.warningForeground": "#c24038",
        "editorWarning.foreground": "#c24038"
    }

to compensate in the short term.

Consider updating the theme to specify colors for those, so that the theme will be consistent regardless of VSCode updates.

Issue Analytics

State:
Created 4 years ago
Reactions:6
Comments:10 (4 by maintainers)

Top GitHub Comments

5reactions

louis-laucommented, Aug 5, 2019

I’ve been confused for the past day why the hell warnings were showing up as errors in vscode. Guess they weren’t. I’m still confused by the choice to make warnings dark red and errors a slightly brighter red.

Warnings aren’t red in atom either.

3reactions

Binaryifycommented, Aug 7, 2019

@cyberbit @louis-lau @grovertb @Dreamacro @ford04 sorry for that, will change it be yellow, but not the default yellow for more coordinated