#What does Figma consider s change in a library file?

5 messages · Page 1 of 1 (latest)

main forum
#

I'm trying to understand where some seemingly random changes come from when I go to publish updates in our components library file? Is some thing a simple as selecting a frame or layer get registered as a modification? Is this documented anywhere?
Thanks

scenic quest
#

Same here, we often have the case, especially in larger design systems, that changes appear which have to be published and it's unclear what has changed. The history doesn't help in that case. Even by adapting a "core design system team of ±3 editors" still leads to weird changes sometimes. Are there any best practices @late bough @minor sun ?

scenic quest
#

And is it possible to search within the history? We use "Add to version history" to save/document critical changes. But how can I find them again?

minor sun
#

Hi andywd7 and Alex! Thanks for sharing this!!

I'd have to do more digging on what exactly qualifies as a change for a main component (for example, will an accidental 1px movement register a change); in the mean time, please continue testing and file any bugs if you think it's a bug! 🙏 🙏

On searching in version history, cmd+f does work while browsing older versions, but it will only search from the listed types (image)—which might not tell you enough info

image.png
wet hamlet
#

Hey everyone. So I think I can help since I’ve been dealing with this for years now 😅

So, Figma considers updates a few things:

  1. Any new object inside a component frame.
  2. Any layer being renamed.
  3. Any change in written content.
  4. Any change in the properties that can be seen on the properties panel on the right side under the Design tab.
  5. Any change in nested component instances or styles.

This means that yes, 1px move would trigger a library update since it falls under point 4. Now, the issue you’re complaining about seems more like one of those persistent Figma bugs, many times coming from either complex component architecture or just because the software is wrongly interpreting some action.

In any cases, hope my answer attached to @minor sun’s is enough to clarify. And please do report any weird behaviors to support and it will help a lot with identifying and solving any of those bugs.