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
First of all, I am so thankful for this amazing project, it really has changed a lot of things for me.
I have a question which I'm struggling with at the moment. I want to create my own properties for typography, this is so I can have it available for Figma tokens:
I've been struggling with this and would love for someone to help if possible. One thing I've noticed. With my custom transform I've managed to get close, but when the property with the alias add it's own "fontSize": {"value": "1rem"}. Which ends up looking like this:
Hey, thanks for the question. Unfortunately I'm not entirely sure what you are trying to do. I'm not sure what mapValue is for or how you are trying to use the alias resolving internal to SD.
I can tell you that any token with a value property will attempted to be resolved by SD, and aliases using the "{}" notation will be resolved to the representation in the dictionary that exists for the dictionary value located at the place referenced by the alias.
Hi guys,
First of all, I am so thankful for this amazing project, it really has changed a lot of things for me.
I have a question which I'm struggling with at the moment. I want to create my own properties for typography, this is so I can have it available for Figma tokens:
I want to be able to add a custom transform that will output the values like so while still applying the alias values:
I've been struggling with this and would love for someone to help if possible. One thing I've noticed. With my custom transform I've managed to get close, but when the property with the alias add it's own
"fontSize": {"value": "1rem"}
. Which ends up looking like this:Anyway I hope this was enough to get my point across! Any help would be very appreciated.
Thanks in advance!
EDIT: I think this relates to #695
The text was updated successfully, but these errors were encountered: