Skip to main content
Question

Why do component instances break so easily?


MiloW
  • Active Member
  • 48 replies

I’ve been working on a project with a branch configuration of Figma.

One pain is that branched components have to be merged so that they are usable throughout other branched designs… so I had to copy them “locally”.

 

main

  • branch1 (e.g. component1)
  • branch2 (e.g. component2)
  • branch3 (a design)
  • branch4 (another design)

so I had to copy component1 and component2 to branch3 and branch4.

 

And then, when I merged branch1 and branch2, an even one change in the component in branch½ as compared to their copies in branch3 or 4 meant crashing the instances in branch3 or 4…

Why is that so?

Even if I add something tiny, shouldn’t the structure try to reflect the previous structure… and maybe propose something like - be careful - we have this and that in a different way - choose what to do now… and then e.g. you choose how a particular setting of an instance is reflected from the newly merged component?

 

E.g. I have in branch1 an input and it has states like hover, etc.

then I copy it to branch3 and 4 so that I can use it in my designs. (BTW - why isn’t there like “linking” between branches? or maybe there is and I don’t know it?)

and then I make just a tiny change in component in branch1, merge it to main

distribute it to branch3 and 4… and the instances of the component get broken : /

Why is there no options, no alert - “be careful, this component was changed, please review the changes” - why isn’t there component-level comparison? Component feature-level comparison…

 

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings