Skip to content
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

Closed
travisbashor opened this issue Aug 1, 2019 · 10 comments
Closed

Updated VSCode Warning Colors Do Not Match #324

travisbashor opened this issue Aug 1, 2019 · 10 comments

Comments

@travisbashor
Copy link

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.

@Binaryify
Copy link
Owner

could you provide a screenshot about what it can change

@travisbashor
Copy link
Author

Sure thing. Those are the default colors below. I replaced the yellow with the red above, but I think even that red might be a little too dark. It was just better than the yellow :)

VSCode Default Colors - Editor and List

@Binaryify Binaryify added the WIP Work In Process label Aug 3, 2019
Binaryify pushed a commit that referenced this issue Aug 3, 2019
@Binaryify
Copy link
Owner

just release a new version, you can check it now

@Binaryify Binaryify added enhancement and removed WIP Work In Process labels Aug 3, 2019
@cyberbit
Copy link

cyberbit commented Aug 5, 2019

I'm confused why editorWarning.foreground was changed to (1) red and (2) a red that doesn't even match the rest of the theme:

image

IMHO the switch to a yellow color for warning squigglies was better for visually grepping a file for linter issues vs. compile issues.

@louis-lau
Copy link

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.

@grovertb
Copy link

grovertb commented Aug 6, 2019

You should think about returning to the yellow warning color, because it is confusing to have the error and warning be red.

@Dreamacro
Copy link

Dreamacro commented Aug 6, 2019

I spent a lot of time thinking about why warning is red. please revert this change. BTW I use golint

@ghost
Copy link

ghost commented Aug 6, 2019

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:

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

@Binaryify
Copy link
Owner

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

Binaryify added a commit that referenced this issue Aug 7, 2019
@Binaryify
Copy link
Owner

Binaryify commented Aug 7, 2019

just release a new version~ thanks for all feedback
also @travisbashor don't be discouraged, the default colors are really incongruous, now this theme become more better than before~

Binaryify pushed a commit that referenced this issue Aug 8, 2019
Binaryify added a commit that referenced this issue Aug 8, 2019
Binaryify added a commit that referenced this issue Aug 8, 2019
Binaryify added a commit that referenced this issue Aug 8, 2019
Binaryify added a commit that referenced this issue Aug 8, 2019
Binaryify added a commit that referenced this issue Aug 8, 2019
Binaryify added a commit that referenced this issue Aug 8, 2019
Binaryify added a commit that referenced this issue Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants