Store component with states in CC Libraries
I noticed that if I add a component with multiple states to the shared library, only the currently active state is stored. Please allow storing the components with all of its states in the library.
My Design Team is also waiting for this ...
I'm also waiting for this option - why is so huge difference between build-in components and CC library. It should be working the same way.
Tina Bonis commented
Is this something planned for a new update? It's been more than 3 months we are all waiting to be fixed. For now states can be used only in small projects.
Agnieszka Kostrzewa commented
I started use components option some time ago and see one thing that doesn't seem to work with CC Library. When I add component there and copy from library to another project it seems to see only default state.
It is quite surprising as updating components in the original file updates all changes in any instances within other files when I just copy/paste them between files. Why the same doesn't apply to the component added to library? Am I missing some sync option here?
Paul Popa commented
We have a very complex design system within our company, and it is imperative for us to have the components stored with their associated states as well. Otherwise, the components states feature becomes redundant, isn't it?
At this point, I'm very annoyed with this issue, since it didn't cross my mind to check if the states will be added to the CC library as well. And now, I'm sitting here with a few hundred components that I cannot add to the CC library since they cannot be used anyhow.
I'm not even starting to talk about the time invested in "converting" all the components to have states — prior to the component states feature, we had created and used one component for each state.
Sam Jacob Dev commented
@logan Exactly I share your pain.
Is this something planned for a new update in the near future?
It's essential for our work as a team.
I mean, component states are XDs biggest differentiator. How can you not A) support them in your own library system, and B) not make them function cleanly enough for users to tell the difference between limitations and bugs?
Building a wireframing component library that my team can use across projects has become futile due to the lack of support for component states in CC libraries coupled with XDs inability to maintain nested component overrides from the master component into instances (is this a bug or a feature, I can't tell).
I now have to tell my team to open the library file and copy/paste **only master components** that they need into their working file. Not exactly "at the speed of thought", XD. Seems like I'm actually devoting more and more thought to work-arounds for XDs limitations.
Yes, that's correct. We use a shared library as a team of designers, and just found out that it doesn't store the component states (that we extensively use).