Versioning for Components

[stedben]

Hello Florian,

Thank you for this awesome plugin! I saw on the Figma plugin page, a commenter requested tracking versions of components. This would be very helpful for my use case as well.

All the best,
Ben

[florianb]

Hey @stedben - thank you very much! I am not using components by myself. I don't know how an expected functionally might look like.

When i enable a component, i am able to attach versions to all parts of the component.

Can you help me to understand what yopu're missing?

Thank you - Florian

[florianb]

After fiddling around i guess i get it - this issue is about "published" components right? Would it be possible to somehow share a Figma Board where the issue is visible?

[renelopezgomez]

Hey guys, I hope this makes it more clear: https://www.figma.com/file/ETqLGYW99AzeFChxZpAOse/Semantic-component-versioning?node-id=0%3A1&t=WbfzXALRHljG8Znv-1

[florianb]

Hey @renelopezgomez - that's awesome, thanks!

As far as i understand the issue now these kind of changes would require to somehow apply changes (update the version in the name or in the description) as soon as a node is updated by the user (by changing the node's type, creating a copy, changing the name).

I guess in order to do that i'd need either that the Figma API notifies about a relevant change (i am not sure that this is possible) or that the plugin is run after that change allowing a quick fix.

I am not sure if an automatic fix would be desirable since it could quickly mess up your applied versions.

[romu70]

Hi. I repost my comment on Figma here:

Thank you so much for such a great plugin, really helpful.

Feature request: we use Figma variants to keep components versions. That's a way to see how a component evolved over time and this way we're able to test a new version of a component in the design by simply changing the value of the "version" property.

And it would be really great if your plugin could handle version tagging on component variants directly as it does on components.

Here a sample library file: https://www.figma.com/file/NsMXDYlDOr9uRoVUGbvV0Q/test-lib?type=design&node-id=12%3A4&t=H7smpsUfCwVTE7hU-1

Of course, component variants are not meant for version control, that's a trick, and it requires to keep components as lean as possible in order to prevent having too much variants.

The first idea I've in mind for the plugin would be to handle a kind of hidden property, ".version" or... "@Version", entirely handled by the plugin.