Skip to main content
Zoltan_Szalay
September 22, 2022

Expose/hide nested instances -> at component property level

  • September 22, 2022
  • 381 replies
  • 20389 views

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure.
Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component.

What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

381 replies

Dflta
November 28, 2024

@Figma came on, do something

ThuyAnh
New Participant
December 3, 2024

Tbh I don’t think they’ll do anything. Not if all the admins turn a blind eye to this. They go out of their way to changes things here and there just because, things that no one ask for except their bored product designers, but they absolutely ignore what users truly want when it’s hard.

Hard things are lame. What’s cool is trying to prove you’re good at ux designing. Apparently good ux is letting users get use to one behavior, let them form muscle memories, let them do things out of habit, then proceed to change how things work out of nowhere, without any surveys beforehand. Wait for several months for users to finally figure things out on their own and come to terms with new changes, they repeat the whole process again.

lx-zd
December 3, 2024

What if instead of having an AI design a weather app for me, I could choose which properties of a nested component I surface to consuming designers, helping to prevent errors and drastically improving quality of life? Wouldn’t that be crazy?!

Rudolf
December 5, 2024

Absolutely necessary +1

Imani_Joy_Maia
December 6, 2024

I was shocked to learn today that this important feature isn’t yet supported. It’s definitely preventing me from setting up intuitive but powerful components that our team can use without overriding properties that should be locked.

Figmashley
New Participant
December 12, 2024

+1000! This would be so helpful 🙏

Evie_Zhang
New Member
December 17, 2024

@Figma Any updates on this one?

Connor_Larsen
December 17, 2024

This feature would be a huge quality of life improvement and would streamline the structure of a bunch of our components while making them easier for consuming designers to use. Please @figma_support tell us you’re at least exploring how to make this feature work

mnakhli
New Member
December 23, 2024

+1000… 👌t2:
This feature would be highly practical. I’ve been struggling with this for a while, especially when trying to declutter complex components and streamline their usability. It would greatly enhance the workflow and component organization. Please prioritize adding this functionality soon! 🙏🏼

Yassi_Hm
December 23, 2024

this feature will change and improve the quality of the design and design system. it will make it easier for us to work with complex components.
Please tell us some good news and put this one as a high priority.