fix: generate dark mode overrides for tokens referencing other tokens - #132
Closed
TrevorBurnham wants to merge 8 commits into
Closed
fix: generate dark mode overrides for tokens referencing other tokens#132TrevorBurnham wants to merge 8 commits into
TrevorBurnham wants to merge 8 commits into
Conversation
TrevorBurnham
requested review from
ernst-dev
and removed request for
a team
December 16, 2025 15:53
2 tasks
The resolveToken function was returning CSS variables for any token that existed in propertiesMap, including regular token-to-token references like colorBackgroundTableHeader → colorBackgroundContainerHeader. This caused both light and dark modes to resolve to the same CSS variable string (e.g., var(--color-background-container-header)), so the difference() function couldn't detect any difference between modes and didn't generate dark mode overrides. The fix restricts CSS variable resolution to only reference tokens (palette tokens like colorPrimary500) by using isReferenceToken() instead of checking token existence. This allows regular token references to continue resolving recursively to their actual values, enabling proper light/dark mode comparison and override generation.
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Joan Perals Tresserra <jotresse@amazon.com>
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
The resolveToken function was returning CSS variables for any token that existed in propertiesMap, including regular token-to-token references like colorBackgroundTableHeader → colorBackgroundContainerHeader. This caused both light and dark modes to resolve to the same CSS variable string (e.g., var(--color-background-container-header)), so the difference() function couldn't detect any difference between modes and didn't generate dark mode overrides. The fix restricts CSS variable resolution to only reference tokens (palette tokens like colorPrimary500) by using isReferenceToken() instead of checking token existence. This allows regular token references to continue resolving recursively to their actual values, enabling proper light/dark mode comparison and override generation.
ernst-dev
force-pushed
the
fix-dark-mode-overrides
branch
from
July 7, 2026 14:58
ef2de0b to
7abe6a1
Compare
pan-kot
requested changes
Jul 10, 2026
pan-kot
left a comment
Member
There was a problem hiding this comment.
I looks like we attempted a similar fix here: #164
The PR was closed because that particular problem has gone after this PR: #163
@TrevorBurnham, please check if the changes in this PR are still needed, or close it otherwise.
Author
Confirmed: This is no longer needed. |
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
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.
Fixes cloudscape-design/components#4111
#130 introduced a bug where the
resolveTokenfunction returned CSS variables for any token that existed inpropertiesMap, including regular token-to-token references likecolorBackgroundTableHeader→colorBackgroundContainerHeader. This caused both light and dark modes to resolve to the same CSS variable string (e.g.,var(--color-background-container-header)), so thedifference()function couldn't detect any difference between modes and didn't generate dark mode overrides.The fix restricts CSS variable resolution to only reference tokens (palette tokens like
colorPrimary500) by usingisReferenceToken()instead of checking token existence. This allows regular token references to continue resolving recursively to their actual values, enabling proper light/dark mode comparison and override generation.cc @jkuelz
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.