Skip to main content
Solved

Testing library updates before publishing

  • November 10, 2022
  • 5 replies
  • 729 views

Rockytori

Hello!

Does anyone know if there’s a way for me to test the impact of the changes I’ve made in the library before publishing it? There were a couple of times I’ve noticed that the updates I made reset the content (my fault for restructuring layers, renaming them, etc). But now I’ve got PTSD and I just really need to make sure that when designers get the update, nothing gets broken.

Thanks!

Best answer by Pavel_Kiselev

Hey

Publish pre-release version and try it on a file. You can swap libraries to see how it would work. Don’t forget to back up test file though )

View original
This topic has been closed for comments

5 replies

Pavel_Kiselev
  • Power Member
  • 438 replies
  • November 11, 2022

You can make exact copy of the file you about to publish, I would name something like “Pre-Releas Test Build”. Work with the new copy, but does not hold swapped we need to quickly now you can test your designs


Jeppe_Boutrup_Nielsen

Hi Pavel,
So how would you test if your “Pre-Release Test Build” breaks anything in a consuming team’s main design file?


Pavel_Kiselev
  • Power Member
  • 438 replies
  • Answer
  • November 22, 2022

Hey

Publish pre-release version and try it on a file. You can swap libraries to see how it would work. Don’t forget to back up test file though )


Jeppe_Boutrup_Nielsen

Thanks for the quick clarification! I’ll try that out 🙂


Pedro_Batista

but swap libraries doesnt seem reliable on a component with variants specially with colors


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