Nested Instances are hidden by default in UI3

Forum|Forum|2 years ago
July 1, 2024
13 replies
3456 views

We spend so much time utilizing and shaping nested instances in our components. In UI3, they collapsed by default, which feels like a buried functionality for DS that utilizes wrappers and slot architecture.

The decision to hide nested props makes no sense. We won’t use nested props if we don’t need to expose nested instances on a high level. Selecting which props from nested to expose and hide not exposed would be much more useful to keep a clean UI.

Alexandre_Navarro_Caldeira

I agree. We put lots of effort into making components more flexible and maintainable using nested instances. Hiding the nested properties will result in much more training sessions to the teams if we don’t want components to be detached.

Michael_Staton

New Participant

I don’t have access to UI3, but I can tell you I have spent months of time nesting components inside components so that any change will propagate correctly across our designs.

So, I’m voting this up. Nested Instances, Local Variables, Modes, etc are THE features that, if used correctly and with vigilance, should help our team move faster and faster.

Michael_Staton

New Participant

Could you share screenshots of how deep your nesting goes? I did and got a lot of “woah, that’s insane.”

Bauke_Schildt

Active Member

I’m pretty sure it is because they moved Instance properties up in the Sidebar, which means the Position/Layout pane is sometimes out of sight on Complex Components.

It’s… a choice

T

thisisbusungko

I’ve just found it. You can access to add nested instance via [+] icon button besides “Properties” on the right panel especially when you hover that area. Check the image that I attached.
Screenshot 2024-08-01 at 4.16.25 pm

Belhimer_Abderrahmane_Adel

This helps thank you so much man!

Tatiana_Anagnostaki

Thank you for showing this. I have to say that it doesn’t make sense to show the “+” icon only on hover, because the “Properties” title itself looks “disabled” by default, and it doesn’t provide any affordance to the user. This is something that I’m not fond of the new UI.