[CB] Replace material ui with native css variables and tailwind utilities#4188
Conversation
45a3d76 to
53ef45a
Compare
…-variables-and-tailwind-utilities
SychevAndrey
left a comment
There was a problem hiding this comment.
This is a big step forward to clean CSS in the project! Good job. 👍🏻
Please check noted places and let's try to use css nesting more and don't forget about layers.
webapp/packages/core-theming/src/styles/utilities/elevation.css
Outdated
Show resolved
Hide resolved
| */ | ||
|
|
||
| .cm-tooltip.cm-tooltip-autocomplete { | ||
| & > :global(ul) { |
There was a problem hiding this comment.
you use :global here, but this css file is not .module.css
plus for plain css we should use @layer
webapp/packages/plugin-codemirror6/src/theme/_base-code-editor-tooltip.css
Outdated
Show resolved
Hide resolved
webapp/packages/plugin-codemirror6/src/theme/_base-code-editor.css
Outdated
Show resolved
Hide resolved
| background: var(--theme-sub-secondary) !important; | ||
| color: var(--theme-on-secondary) !important; | ||
| } | ||
|
|
||
| & li[aria-selected='true'] { | ||
| background: var(--theme-secondary) !important; | ||
| color: var(--theme-text-primary-on-light) !important; |
There was a problem hiding this comment.
it wasn't !important in scss varian, why it changed?
…-variables-and-tailwind-utilities
This reverts commit 78229ac.
This reverts commit 20ca1b7.
…-variables-and-tailwind-utilities
Wroud
left a comment
There was a problem hiding this comment.
there are a lot of places where shadows / gaps / transitions / animations inlined in the specific styles, they all probably should be part of the design system, not just independent styles for specific components
webapp/packages/core-blocks/src/FormControls/Checkboxes/Switch.module.css
Show resolved
Hide resolved
webapp/packages/core-blocks/src/FormControls/Checkboxes/Switch.module.css
Show resolved
Hide resolved
| background-color: currentColor; | ||
| border-radius: inherit; | ||
| pointer-events: none; | ||
| transition: opacity 150ms linear; |
There was a problem hiding this comment.
is this is unique transition, or it should come from the design system?
There was a problem hiding this comment.
moved to design system
webapp/packages/plugin-codemirror6/src/theme/base-code-editor-autocompletion.css
Outdated
Show resolved
Hide resolved
webapp/packages/plugin-tailwindcss-theme/src/PluginTailwindcssThemeBootstrap.ts
Outdated
Show resolved
Hide resolved
| --duration-micro: 90ms; | ||
| --duration-fast: 100ms; | ||
| --duration-normal: 150ms; | ||
| --duration-medium: 200ms; | ||
| --duration-slow: 300ms; | ||
| --duration-slower: 350ms; | ||
| --duration-slowest: 500ms; |
There was a problem hiding this comment.
do we sure that we need so many of them?
can we choose between 90 and 100 and keep one?
150 and 200?
300 and 350?
for example:
100
200
350
500
| --ease-linear: linear; | ||
| --ease-soft: ease; | ||
| --ease-in-out: ease-in-out; |
There was a problem hiding this comment.
--ease-linear: linear;
--ease-in-out: ease-in-out;
naming usually should not reflect implementation, but purpose or some abstraction
for example, --ease-default: linear;, --ease-action: ease-in-out;
…-variables-and-tailwind-utilities
| height: 16px; | ||
| padding: 0; | ||
| transition: transform ease-in-out 0.2s; | ||
| transition: transform var(--duration-medium) var(--ease-smooth); |
| opacity: 0.5; | ||
| transform: rotate(-90deg); | ||
| transition: transform 0.15s ease-in-out; | ||
| transition: transform var(--duration-medium) var(--ease-smooth); |
…-variables-and-tailwind-utilities
closes https://github.com/dbeaver/pro/issues/8433