-
-
Notifications
You must be signed in to change notification settings - Fork 79k
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
Move reassigned Sass maps for colors to another stylesheet #34942
Conversation
This looks fine to me, and totally makes senses. 👌 It needs some docs indeed, and we must ensure we're not forgetting any example somewhere. |
70533dc
to
6a51dea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, the migration guide is very clear 👌 Thanks!
Hi @mdo, |
Fixes #34756.
The intent of the new CSS variables and the Sass maps that power them was improved customization, but it complicates things and breaks a common workflow. There's no great way around this unfortunately as the problem is how we create new variables and maps based on existing ones. For example, we extend
$theme-colors
into$theme-colors-rgb
and two maps for.text-*
and.bg-*
utilities. As of v5.1.1, those other maps do not get updated after$theme-colors
are modified.There are two viable solutions I can see:
variables
and the newmaps
so they can be updated accordingly. Like so:Todos
/cc @twbs/css-review