Open keeganedwin opened 1 year ago
What if, instead, we'd
.
in the style namesRename styles from . to /
and Cancel
Added to Featurebase Roadmap as a known issue to test and track with V2 beta testers - ❖ 🪄 Sync variables and styles is now Export to Figma
@keeganedwin I'm not able to replicate this issue anymore in the V2beta build. Can you test please and if you also can't replace we can close this issue.
@SamIam4Hyma @six7
I'm still able to replicate this in both Published 38.9
and rc8
.
Since the plugin imports style.1
and style.2
as a group, it has a different structure than the styles setup in Figma, and so if you try to create styles (sync does not work) it creates a color group called Style
with 1 & 2.
Describe the bug When creating Figma styles and importing them to the plugin, users are unaware that the naming convention in Figma has to follow a
Style/name
format in order for the styles and tokens to sync.To Reproduce:
style.name
.Key Information: user created the style following the plugin's naming convention
style.name
, and on importing and changing the token reference from the plugin, the style in Figma would not updatehttps://user-images.githubusercontent.com/93133012/229492095-f9c66339-ede3-458a-874c-5aa9520aad6a.mov
Proposal: On importing styles the first screen should have a model informing that the correct naming conventions for the styles should be used in order to sync with the plugin
And then proceed to the screen with the modal to import the type of styles: