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
I'm also noticing the ability to just pass through token values that don't necessarily map to one of your existing formats. Might be worth allowing a general type/category for this.
The text was updated successfully, but these errors were encountered:
Nevermind—the hex issue was totally my fault. This works fine. I'd still love your thoughts on being able to add other design tokens that might not fit into the categories you provide (even though they are thorough).
@julzmon I wound up adding colors to my _aliases.yml file like this:
aliases:
#colors
white: '#fff'
black: '#000'
Then I created a _color.yml file where I have the following:
imports:
- _aliases.yml
props:
white: "{!white}"
type: color
category: text-color
comment: ""
black: "{!black}"
type: color
category: text-color
comment: ""
Then obviously import _color.yml into your main app.yml file. This seems to get around not having categories that map since I'm just using this to generate the tokens, not the styles doc.
Unless I'm missing something, if I have the following in my
aliases.yml
:The output doesn't read hex values and I get:
...for all colors.
I'm also noticing the ability to just pass through token values that don't necessarily map to one of your existing formats. Might be worth allowing a general
type/category
for this.The text was updated successfully, but these errors were encountered: