Skip to main content

Nested Instances are hidden by default in UI3


Dflta

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.

13 replies

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

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

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


Bauke_Schildt

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


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.


THANK YOU!
Thank f#$^ing god! I almost just had a panic attack in a meeting because I could not find this. WHY THE EFF IS IT HIDDEN WITH A HOVER?!


ignaciogiri

Thank you! I spent half hour looking for it.


Jarek_Marciniak2

Just spent hours to figure out if my UI is bugged or I’m missing an update… why is this hidden jesus christ 😭

Thank you.


Thomas77
  • 1 reply
  • September 23, 2024

Thank you for this guys, it’s already mind blowing to me that we have to use the community to find a feature like this.


RJ_Nye
  • 1 reply
  • October 4, 2024

Thank you for bringing this up and to those who posted the “solution”. I had to revert back to the original UI to continue my work before I was able to investigate the “new” way to create component properties. What an odd decision for UI3.


dvaliao
Figmate
  • Community Support
  • 4666 replies
  • October 4, 2024

Hey All, thanks for the feedback!

The UI3 team is already working on improving the discoverability of certain features in UI3. We’ll pass this topic onto the team for improvement.


Reply


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