Skip to content

feat(color): add seed variables for palette colors#573

Open
didimmova wants to merge 2 commits into
masterfrom
didimmova/add-seed-variables
Open

feat(color): add seed variables for palette colors#573
didimmova wants to merge 2 commits into
masterfrom
didimmova/add-seed-variables

Conversation

@didimmova
Copy link
Copy Markdown
Contributor

Closes #520

@didimmova didimmova requested a review from simeonoff May 20, 2026 07:01
@didimmova didimmova added ❌ status: awaiting-test PRs awaiting manual verification palettes labels May 20, 2026
) {
$color-shades: types.$IColorShades;
$gray-shades: types.$IGrayShades;
$gray: if($gray, $gray, if(luminance($surface) > 0.5, #000, #fff));
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is weird, it's already handled by the shade function. There's a special clause that already extracts the luminance of the surface color in regards to the gray shade. Honestly, I don't think that extra step is needed. Instead of doing it the way you're doing it now, it's my strong conviction that you can add a "seed" value to the Color Types ($IGrayShades, and $IColorShades), and have a modifier of 1 for the static multiplier maps for for both the gray seed and the color seed variants. The shade function will just produce another color "shade" - seed then. The shades function stays the same as it is today (bar the bug fix you introduced for the error color).

Does that make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

palettes ❌ status: awaiting-test PRs awaiting manual verification

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Palettes: Custom base gray color modified when creating shades off it

3 participants