Component states to inherit interactions from master default state
Component states should behave like component copy instances. This includes interactions to be copied to all child states. This is essential, for example, for a menu component in which each state is the active status of each menu item. But when I create new state it loses all interactions. Maintaining 5 states with 5 menu items becomes tedious.
Harun Alikadić
shared this idea
6 comments
-
digita
commented
Any news? Because there is too much manual work for edit states.
-
John Vanore
commented
component instances - update to default state should automatically update non customized properties for all other states. This is currently the behavior in the master component; when you update a property in the default state, and that property has not been customized in other states, the other states inherit the change made in the default state. This behavior is not the same in instances of the component however. Similarly, if I cut or paste from/to the default state, that element should be cut or pasted from/to the other states as well. It works this was in the master component states, but not the instances. It should be a consistent experience, but it's not. The result is needing to make the same change many times over throughout all the states. When you have components nested within other components, the issue is magnified. The time it takes to make these changes quickly adds up.
-
Rob Lee
commented
I use buttons a lot, if I change the label in the default state, it should change the label across states. I have to update 4 states on every button.
-
Matthias Ott
commented
+1! This is super important IMO. It already works for the master component but not for other instances of the component. Also got this feedback in one of the XDI workshops. Great to hear that you are on it! :)
-
Joe commented
+ 1 for this! *goes back to wiring states to 100 components*
-
Hi Harun. Thank you so much for posting your feedback. This is definitely something we are working on. We agree that you should not have to manually maintain syncing across states and instances, so we are definitely on it. Stay tuned because it's definitely on its way.
