All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning
- Use lighter neutral color for object properties
- Use different color for intermediate properties
- Use default color for constant name
- Use red for tags. It has better contrast next to attributes and functions
- Use deep purple for directives to maintain consistency
- Use orange in the component tag when the language mode is Javascript
- Use white in the tag's inner text when the language mode is Javascript
- Use default color (neutral) for punctuation to maintain consistency
- Add Universe Gray variant
- Use darker grey in punctuation marks. They are less relevant than the rest of the code, this change prevents them from standing out
- Use neutral for object property instead of the strings' green
- Use darker color for text
- Use object property color (neutral) for native objects properties
- Use same color when defining or accessing an object property
- Improve the wording at "Different syntax highlighting"
- How to fix syntax highlighting problems?
- Add color for unfocused active background. Fixes #50
Pull request #48
- Use blue in attribute selector punctuation
- Use property name color (green) in media query property name
Pull request #49
- Use yellow and bold in headings
- Use neutral in heading punctuation, list punctuation, and separators
- Use green in bold text
- Use teal in italic text
- Use blue in the code blocks
- Use text color in paragraphs
- Use lighter blue in the link titles
- Use darker blue in link punctuation
Pull request #50
- Use yellow in document puntuaction
- Use deep purple in block mapping puntuaction
- Use deep purple in directives
- Use neutral color in sequence item punctuation
- Use deep purple in merge keys
- Use variable color (pink) in anchors
Pull request #43
- Use custom type color (cyan) in fragments' name
- Use the variable's color (pink) in alias
- Use custom type color (cyan) when defining a custom scalar
- Use object property color (green) in types and interfaces' fields
- Use object property color (green) in selection set fields
- Use comment's color (gray) in descriptions
Pull request #45
- Use italic in other operators (
in
,of
,typeof
,instanceof
) - Use pink in language variables (
console
andwindow
) - Use yellow in classes' name
- Use deep purple in template expression punctuation (
${ data }
)
Pull request #45
- Use white in tag's text
- Use orange in expression punctuation (
{ data }
) - Use orange in component tag (
<MyComponent/>
)
Pull request #44
- Use gray in comments
- Use HTML tags' color (cyan) in doctype
- Use green in the path when including a file
- Use deep purple in string interpolation punctuation
Pull request #46
- Use green in enums members
- Use cyan in type punctuation
- Use yellow in
Math
class - Use cyan in the extended interface
- Use italic in
keyof
operator
- Add italic variants: Universe Italic and Universe Purple Italic. #41
- New logo: It's more minimalist and uses simple shapes. #40
- Use constant color (teal) in JSON object. #41
Changes that affect user interface and syntax highlight
- Delete indigo and light blue palette: both are similar to blue
- Delete gray palette: there is already a palette with neutral colors
- Delete light green palette: It's similar to green
- Use teal for language constants and other constants
- Use cyan in native types
- Use blue in special characters
- Use HTML tag color (cyan) in the tag selector
- Use HTML attribute color (blue) in attribute selector
- Use object property color (green) in the property name
- Use blue in property value
- Use modifier color (deep purple) in pseudo classes and pseudo elements
- Use orange in numbers and units
- Use cyan in HTML tags
- Use red color in directives. Eg. Vue and Angular directives
- Use same color in tag punctuation
- Use deep purple in constants
- Make comments have less contrast
- Use yellow in classes names: use a color that differentiates them from functions and methods
- Use green in object properties
- Update the neutral color to use background hue. It's used in activity bar icons and text
- Make activity bar icon's foreground darker
- Use saturated color in error text
- Use saturated colors for file status when using Git
- Use a lighter background in input validation
- Use saturated color in text status within lists
- Use secondary color in Settings' modified indicator
- Use saturated colors in squiggles
- Use lighter white text color in the terminal
- Update colors: the previous palette had both desaturated colors (most of them) and very saturated colors (yellow and orange)
- Use same foreground swatch in git colors
- Use a transparent background in diff editor: It makes reading the code easier
- Use primary color in border of activated options in input fields: It has much more contrast
- Make title bar text and sidebar text lighter: It has more contrast
- Add a deep purple variant. You can select it going to
Settings > Color theme > Universe purple
. - Add the main colors and their usage in the color reference in the README. #2
- Changed the background hue to deep blue.
- Use defined colors for an element in all languages: green for
strings
or orange fornumbers
. - Update bracket pair colorizer settings.
- Use the primary or secondary color instead of purple to highlight interface components.
- Many small changes to maintain consistency in the user interface.
- New syntax colors: the new palette is more consistent. Now it's using Material Design colors. The most important changes are that purple is more saturated and green is less saturated. #26
- Differentiate the text using grayscale, according to their importance. #27
- Colorize punctuation from interpolated strings: it was difficult to differentiate an expression within a string. #16
- Make the scrollbar semi-transparent: scrollbar markers weren't visible when covered by the scrollbar. #18
- Use dialog colors in debug toolbar. #19
- Use input colors in dropdowns in the Integrated Terminal and the Output panel. #20
- Use a new color palette for the background: the new colors are more accessible. #6
- Use green and red as
diff
colors: it makes easy to see the changes in files. #1 - Use a darker background in the peek view header and results
- Use gray colors in indent guides and rulers
- Minor changes
- Use blue for functions and classes
- Use indigo in
HTML
attributes: pink is already used in JSX variables
- Use indigo in object keys: the object keys must have different colors than their values to make it easier to distinguish them. Before teal was too similar to the green used in
strings
- Use different colors for each type: now
strings
are green,numbers
are orange,constants
like booleans ornull
are purple, primitives and custom types likeinterfaces
are teal. - Add transparency to some UI components to avoid cover others: if the color is solid you can't see what it is behind it. #11
- Theme preview to README.md
- Initial editor colors
- Initial syntax highlight colors
- Support for
CSS
,GraphQL
,HTML
,JS
,JSON
,Markdown
,Pug
,JSX
,TS
,Vue
andYAML