-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated VSCode Warning Colors Do Not Match #324
Comments
could you provide a screenshot about what it can change |
just release a new version, you can check it now |
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. |
You should think about returning to the yellow warning color, because it is confusing to have the error and warning be red. |
I spent a lot of time thinking about why |
I consciously decided to display my tslint erros with warning color (yellow in recent VS Code). Now it's all one big mess; first I wanted to blame VS Code, then tslint.... until I realized it's my favorite theme having trouble :( . Update: To use default VS Code colors (the yellow one), a workaround is to set settings like this:
|
@cyberbit @louis-lau @grovertb @Dreamacro @Ford04 sorry for that, will change it be yellow, but not the default yellow for more coordinated |
just release a new version~ thanks for all feedback |
In VSCode update 1.36.1, a color was chosen for
list.warningForeground
andeditorWarning.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
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.
The text was updated successfully, but these errors were encountered: