You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem Summary:
When using wrapper mixins (like dark-theme()) and passing a handmade palette with unquoted keys, it causes a compilation error. However, if the keys in the palette are quoted, the error is resolved, and the mixins work as expected.
Unquoted keys in palettes cause compilation errors.
Quoting keys resolves the issue.
EXPECTED BEHAVIOR:
The wrapper mixins (or theme()) should handle both quoted and unquoted keys in handmade palettes, OR
The documentation should explicitly state that palette keys must be quoted to avoid errors.
The text was updated successfully, but these errors were encountered:
desig9stein
changed the title
Wrapper mixins around theme() throw an error when using a palette with unquoted keys
Handmade color palettes throw an error with unquoted keys
Nov 26, 2024
Seems this is only true for the gray color variants. Likely due to the fact that the key is interpreted as color instead of string.
I guess for handcrafted palettes, we should instruct users to define the keys in the map as explicit strings? So that named color keys like gray can be correctly interpolated.
Problem Summary:
When using wrapper mixins (like dark-theme()) and passing a handmade palette with unquoted keys, it causes a compilation error. However, if the keys in the palette are quoted, the error is resolved, and the mixins work as expected.
STEPS TO REPRODUCE
BEHAVIOR:
Unquoted keys in palettes cause compilation errors.
Quoting keys resolves the issue.
EXPECTED BEHAVIOR:
The wrapper mixins (or theme()) should handle both quoted and unquoted keys in handmade palettes, OR
The documentation should explicitly state that palette keys must be quoted to avoid errors.
The text was updated successfully, but these errors were encountered: