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
hi lukas, great to see that you are working on this plugin! i think i really is a great contribution. i was wondering if we could also get into something like a universal transformation, so to say, not limit the plugin to 'well-known' visual properties, but rather think of it as a transformation machine that provides a design token mapping also as an object description machine.
this would, in theory, enable the object transformation from figma to REACT or whatever. lets say, if you had a card object in figma and would then describe it using
which brings us to the missing variables issue in figma: it would then obviously come in handy to assign variables, in the sense of spacings and sizes, and typography, describing those objects (card in the example).
so, no matter how this would be processed then afterwards, i still think it would be a great extension of this plugin in the sense of a universal transformation machine. it might break the transformation pipeline towards something more component-describing, in contrast to have just a set of universal properties as it is currently working. not sure if that makes any sense to you ..
The text was updated successfully, but these errors were encountered:
If this is still something you are thinking about, could you elaborate how you think this could work with figma? Are you saying you would want to export all components and transform the properties in the way you mentioned above?
hi lukas, great to see that you are working on this plugin! i think i really is a great contribution. i was wondering if we could also get into something like a universal transformation, so to say, not limit the plugin to 'well-known' visual properties, but rather think of it as a transformation machine that provides a design token mapping also as an object description machine.
this would, in theory, enable the object transformation from figma to REACT or whatever. lets say, if you had a card object in figma and would then describe it using
_tokens/card -> card/padding
_tokens/card -> card/typography-headline
_tokens/card -> card/typography-p
which brings us to the missing variables issue in figma: it would then obviously come in handy to assign variables, in the sense of spacings and sizes, and typography, describing those objects (card in the example).
so, no matter how this would be processed then afterwards, i still think it would be a great extension of this plugin in the sense of a universal transformation machine. it might break the transformation pipeline towards something more component-describing, in contrast to have just a set of universal properties as it is currently working. not sure if that makes any sense to you ..
The text was updated successfully, but these errors were encountered: