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
Planning to get more into the weeds next week, but is this just a documentation oversight or was $extensions not yet included? If it's not yet included, does that mean it just won't appear in the Figma side (fine) or will syncing from Figma try to remove it from tokens that had a $extensions in the repo's JSON when updating the $value (not fine)?
Our current tokens have an attributes object we use for the build process and seems like $extensions can serve a similar purpose, but wanted to be sure GitFig wouldn't fight that and didn't see anything in the doc/discussion about it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am evaluating GitFig as a tool for Figma<->repo syncing our tokens.
I was looking over the GitFig doc and saw it recommends W3C Design Token format, but the properties listed are only the basics and do not include $extensions which is part of the W3C format.
Planning to get more into the weeds next week, but is this just a documentation oversight or was $extensions not yet included? If it's not yet included, does that mean it just won't appear in the Figma side (fine) or will syncing from Figma try to remove it from tokens that had a $extensions in the repo's JSON when updating the $value (not fine)?
Our current tokens have an
attributesobject we use for the build process and seems like$extensionscan serve a similar purpose, but wanted to be sure GitFig wouldn't fight that and didn't see anything in the doc/discussion about it.Beta Was this translation helpful? Give feedback.
All reactions