-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to set if Variables, Styles or Hex values are applied on applying tokens #2213
Comments
This sounds great! If they change their mind later, how can they switch to an alternate representation? Ex: Variables today, styles tomorrow If the representation doesn't exist any more, like if variables are deleted, then what? Are the settings on the file side, or the plug-in side? If I want to have multiple files using the same tokens can I have 1 file showing styles and another showing variables? This gets into the multiple file sync needs convo. |
I'm going under the assumption that 'Hex' should actually be Raw value? Can you confirm @esthercheran ? |
@LukeFinch yes the raw value |
@SamIam4Hyma would it better to have this setting specific to a document? |
UX Research shows that this feature is desired, but the wording in the design mockups was confusing and most users were unsure that the settings is the best place for this menu option. If we have an "apply to" settings, could it also be accessed there? |
Added to FeatureBase Roadmap : ❖⚙️ Choose to express a token as a style, variable or raw design property |
Will be part of 2.0 RC7 |
When I have tokens linked with variables and styles, I want to set what should be applied on Figma when tokens are applied through the plugin.
Introduce a setting in the settings tab that will allow a default to be set, with each option explained.
This behaviour should happen for all token types depending on whether they are applicable in variables and styles.
The logic of applying the values would be as follows:
Prefer Variables:
Prefer Styles:
Use raw values:
The text was updated successfully, but these errors were encountered: