Skip to main content

Expose/hide nested instances -> at component property level


Show first post

282 replies

Dflta
  • 2 replies
  • November 28, 2024

@Figma came on, do something


ThuyAnh
  • New Participant
  • 12 replies
  • 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
  • 2 replies
  • 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
  • 3 replies
  • December 5, 2024

Absolutely necessary +1


Imani_Joy_Maia

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.


+1000! This would be so helpful 🙏


Evie_Zhang
  • New Member
  • 2 replies
  • December 17, 2024

@Figma Any updates on this one?


Connor_Larsen

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
  • 2 replies
  • 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
  • 1 reply
  • 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.


KennLucas
  • 208 replies
  • December 29, 2024

Users after more than two years desperately needing this: 🤷🏼‍♂️

Figma: 🦗🦗🦗


Katelyn_Barth

Yes please!  I often make based components that I reuse in other instances, and I don’t always want the properties for that base component to show up in nested instances.  This would make it less confusing to use, and clean up the sidebar.


Che_de_Bruin
  • New Member
  • 4 replies
  • January 15, 2025

+1. With complex system, it would be great the limit the number of props exposed on these components, especially nested instances.


r_sh
  • Active Member
  • 25 replies
  • January 17, 2025

+1. We need to be able to limit which nested instance properties show on the main instance level. It gets very confusing for complex components.


Lea.P
  • New Participant
  • 14 replies
  • January 20, 2025

➕1️⃣

For a complex, yet easy-to-use design system, this feature is not an option but a basic requirement.
It must be possible to define at the parent level which individual properties of a nested instance should be displayed or not.

Figma, please implement this as soon as possible, it's really super important, especially for more complex, nested components.
Thanks a lot!


Mark79
  • New Member
  • 3 replies
  • January 20, 2025

This is insane that this has not been done yet. This is an area that Sketch mops the floor with Figma and is the clear winner, the fact that Figma can’t see the issue is incredibly concerning. It makes it incredibly hard to build a set of rich components that you had over to downstream users and they have to make sense out of properties that they should not care about.


Farrech
  • New Member
  • 1 reply
  • January 21, 2025

We need this !


Kamaljeet_Dhiman1

Plus one! Waiting for it eagerly 


Marianne_Rosvik1

This feature MUST be implemented soon! It’s critical for maintaining a scalable and efficient component system. Please prioritize this!


Andre_Edqvist

This is just lame. Nice product management…

Seems like a pretty basic feature but I guess Figma  threw out the roadmap the moment chat GPT entered the room… 

If I recall correctly Sketch has had this for ages…


Mark79
  • New Member
  • 3 replies
  • January 23, 2025
Andre_Edqvist wrote:

If I recall correctly Sketch has had this for ages…

It does. This and auto layout shortcomings are my biggest bugbears at the moment with Figma. Do I care about AI drawing me a box that replicates another design… NO… do I care about building better, more easily understood to downstream users, scalable components… YES. 


Wawa
  • New Participant
  • 8 replies
  • January 24, 2025

Still waiting for this feature


ptk-bankdata

+1. We need this as well.

Has anyone heard anything official from figma? Do we know if its on a roadmap or something?


Kara_Miekina3
  • New Participant
  • 6 replies
  • January 29, 2025

+1 pleaaase!!!


Steven_Chu
  • New Member
  • 1 reply
  • January 30, 2025

+1, I have card containers with cards that support different aspect ratios. If I could show only that one property, instead of ALL nested properties… the panel would be less overwhelming for my designers who use the components


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