Skip to main content

Expose/hide nested instances -> at component property level


Show first post

Simon_Wessely

+1 for this feature. Allowing all nested instances to be visible is giving consumers of our UI Kit the opportunity to tinker and create some very questionable creations.

Make it happen Figma! 😀


Khosbayar_Zolboo

please figma make it happen!


Fred_Erick
  • New Participant
  • February 23, 2023

Ohhhh yes…


Kelvin_Lin
  • New Participant
  • March 15, 2023

This would go a long way in scaling reusable design systems for mid-large teams! I know nesting isn’t always the way to go, but it’s really helpful in many cases still.


Chandler_Simon1

+1, this would prevent a lot of misuse of components!


Renju_Sasikumar

+1 We really need this option, to make immaculate component properties, it will help a lot in different scenarios. also, it can reduce misuse of the proper component.


Sanket_Chaudhari

+1, really really need this.


Maxime_Rodier

I’m very interested by this feature !! For instances hide hover state of a button.


Celine_D
Figmate
  • Community Support
  • April 12, 2023

Hi all,
Thank you for your feedback! I switched this topic to a “Feature request”, so you can vote and we can accurately gauge interest from the community!


Keeping alive, we need this


+1… Really need this feature.


Erik10
  • April 17, 2023

I am actually considering switching to Photoshop or Powerpoint if Figma doesn’t have this feature coming out this year.


AlicePackard

Lol Erik 😂❤️ … SAME THOUGH 😤 (🤪)


Ori_Statlender

+1 This would be really helpful!


Dieter
  • April 24, 2023

This is very useful when using nested instances and I would love to have this feature as well.


JGKIDD
  • April 24, 2023

Bumping! This would really elevate design systems


Florian_Ruee

+1 ! Would be game changer 🥰


StefanieP

+1000 please! 🙏


kendrick

+1

We have some components that are necessarily complex—this would be a massive win for simplicity for our consuming designers!


  • April 28, 2023

+1, this will solve the clutter in sidebar and help us keep components safe from undesired variations


Ash.Sharifi

I am using an instance of a component inside another component variant. I have added the variants property through the nested component features (which is btw awesome and attached a screenshot).

Currently, it imports all the properties from the nested component inside the component. I wonder if there will be a way to hide some properties. For instance more granular check box with every property of the nested instance (Screenshot 2) or renaming the property name with an underscore to hide the property when nested just the same logic on how we hide components from the library. (Screenshot 3) the properties beginning with the underscore _Platform or _Size could be hidden.

Very small fix but it is very powerful to exclude overrides that are unnecessary for certain properties.

image


Mike_Trilford

Yes please, this feature is required.


Matthew_Vella

Yess please. Im working with Interactive components and this feature would be very useful for my design system. I have different size variants of a spinning loader with their own prop Small, Medium, Large. Ive added the loop animation steps for each variant however they require a prop else I get the conflicting error thing. I dont want to give it a prop so hiding component props would fix this.


Casey_Hunt

I am having this exact issue currently. Would love to know a workaround.


Maxime_Rodier

Please, this feature could save my life 🙏 In the meantime, my solution is to place an emoji ⛔ to indicate to the designer to not touch this props


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