fix(tokens): color classes generation from tokens #30725
Merged
Conversation
This file contains hidden or 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
BenOsodrac
added
package: core
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
BenOsodrac
changed the title
BenOsodrac
changed the title
brandyscarney
approved these changes
Oct 13, 2025
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.
Issue number: internal
What is the new behavior?
This pull request makes a minor update to the
generateColorUtilityClassesfunction to improve how CSS custom property values are interpolated in the generated class definitions.core/scripts/tokens/utils.mjs, the function now wraps the SCSS variable reference for the custom property value in#{...}to ensure proper interpolation when generating the CSS class.Does this introduce a breaking change?
Other information