✨💄 Legacy colors override #3518
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oddvernes
force-pushed
the
OOVE/3510-legacy-colors-override
branch
from
93516de
to
e584ec2
Compare
oddvernes
force-pushed
the
OOVE/3510-legacy-colors-override
branch
2 times, most recently
from
43bb831
to
17e6bda
Compare
oddvernes
force-pushed
the
OOVE/3510-legacy-colors-override
branch
from
17e6bda
to
66459a4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #3510
Work in progress. I have extracted all the color override variables from the old tokens into an new css file. Now we just need to hook them up to the relevant new 2.0 variables
TODO: This pr should also install a theme switcher for storybook. Perhaps this one. Ideally we should be able to use our own tokens for the storybook ui as well