mirror of
https://github.com/status-im/consul.git
synced 2025-01-19 02:03:00 +00:00
b8166de30d
From an engineers perspective, whenever specifying colors from now on we should use the form: ``` color: rgb(var(--tone-red-500)); ``` Please note: - Use rgb. This lets us do this like rgb(var(--tone-red-500) / 10%) so we can use a 10% opacity red-500 if we ever need to whilst still making use of our color tokens. - Use --tone-colorName-000 (so the prefix tone). Previously we could use a mix of --gray-500: $gray-500 (note the left hand CSS prop and right hand SASS var) for the things we need to theme currently. As we no longer use SASS we can't do --gray-500: --gray-500, so we now do --tone-gray-500: --gray-500. Just for clarity after that, whenever specifying a color anywhere, use rgb and --tone. There is only one reason where you might not use tone, and that is if you never want a color to be affected by a theme (for example a background shadow probably always should use --black) There are a 2 or 3 left for the code editor, plus our custom-query values
35 lines
628 B
SCSS
35 lines
628 B
SCSS
%code-editor {
|
|
display: block;
|
|
border: 10px;
|
|
overflow: hidden;
|
|
position: relative;
|
|
}
|
|
%code-editor .ember-power-select-trigger {
|
|
@extend %code-editor-syntax-select;
|
|
}
|
|
%code-editor-syntax-select {
|
|
width: 200px;
|
|
float: right;
|
|
z-index: 1;
|
|
}
|
|
%code-editor-syntax-select {
|
|
margin-top: 1px;
|
|
border: 0;
|
|
background-color: rgb(var(--black));
|
|
color: rgb(var(--white));
|
|
border-left: 1px solid;
|
|
border-radius: 0;
|
|
}
|
|
%code-editor::after {
|
|
position: absolute;
|
|
bottom: 0px;
|
|
width: 100%;
|
|
height: 25px;
|
|
background-color: var(--black);
|
|
content: '';
|
|
display: block;
|
|
}
|
|
%code-editor > pre {
|
|
display: none;
|
|
}
|