-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Pink line between editor and breadcrumbs in 0.11.0 #138
Labels
Milestone
Comments
It appears on WebStorm and PHPStorm, even after full plugin reinstallation and ide restart |
arcticicestudio
added a commit
that referenced
this issue
Feb 16, 2020
Fixed the color of the editor & breadcrumbs separator line to use the correct color `nord3` instead of the pinkish "test color" that should only be used during development to quickly identify UI and syntax elements that are affected by a specific theme color key. Thanks to "Tom1206" again for the quick bug report. [1]: https://github.com/Tom1206 Related to GH-125, GH-136 GH-138
arcticicestudio
added a commit
that referenced
this issue
Feb 16, 2020
Fixed the color of the editor & breadcrumbs separator line to use the correct color `nord3` instead of the pinkish "test color" that should only be used during development to quickly identify UI and syntax elements that are affected by a specific theme color key. Thanks to "Tom1206" again for the quick bug report. [1]: https://github.com/Tom1206 Related to GH-125, GH-136 Fixes GH-138
arcticicestudio
added a commit
that referenced
this issue
Feb 16, 2020
Fixed the color of the editor & breadcrumbs separator line to use the correct color `nord3` instead of the pinkish "test color" that should only be used during development to quickly identify UI and syntax elements that are affected by a specific theme color key. Thanks to "Tom1206" again for the quick bug report. [1]: https://github.com/Tom1206 Related to GH-125, GH-136 Fixes GH-138
Released and deployed to the marketplace in version 0.11.1 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably linked to #125 ?
The text was updated successfully, but these errors were encountered: