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
For the Standard Draft, and for StyleDictionary, references/alias must use a 'dot' between groups/children.
However, for organizing styles in Figma, we are going to tend towards using slashes.
i.e. Where the designer creates a style named in Figma as color/grey-10, if they want to use the alias, they have to remember to use a different form of the name: color.grey-10. It would be nice if the Designer did not have to understand the implementation details of the plugin/specification to remember write it in this different way.
I suggest it accept both, but convert any slashes to dots on export.
The text was updated successfully, but these errors were encountered:
Yes, the "ref:" or "alias: " lines in a Description of a colour style for example.
I can probably make a PR, but I can't find the unit test / test data that tests the extraction from the 'description' field. Or is there no test for that?
Hey, I think this is only tested via the integration tests. But I would be great if you could extract this into a separate function and ts file and test it.
Feel free to work on this in small chunks and send PRs for those, e.g. one pr just to "extract and test" the alias functionality. (Small PRs are easier to check and merge for me).
For the Standard Draft, and for StyleDictionary, references/alias must use a 'dot' between groups/children.
However, for organizing styles in Figma, we are going to tend towards using slashes.
i.e. Where the designer creates a style named in Figma as
color/grey-10
, if they want to use the alias, they have to remember to use a different form of the name:color.grey-10
. It would be nice if the Designer did not have to understand the implementation details of the plugin/specification to remember write it in this different way.I suggest it accept both, but convert any slashes to dots on export.
The text was updated successfully, but these errors were encountered: