Skip to main content
Zoltan_Szalay
September 22, 2022

Expose/hide nested instances -> at component property level

  • September 22, 2022
  • 386 replies
  • 20849 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.

386 replies

Bauke_Schildt
Active Member
May 17, 2023

Another option could be a menu on the line of the name of the component

In your example that would be “🔶 IconRight 🎚️🎚️” with a flyout menu to turn visibility of component properties on/off

Edit:

Mockup:
Imgur

Jetto_Gonzalez
May 23, 2023

Please help with this functionality, I remember that when I was working with Sketch they have it and it helped the designers a lot and to maintain consistency in the DS and in the designs and that was about 3 years ago aprox.

Emanuele_Brivio
May 24, 2023

+1 this is really needed also for us, exposing all the properties for some complex component is not useful, but being able to select which one to expose would solve our isse!

May 26, 2023

image
Here is a Select input component I am working on. The label is a separated component with different states and content property for the text.

I want the parent component to show the “label content” whereas I don’t want user to be able to change the state of the label.

I think we can have a convention where the “_” or “.” in front of the property can make it “local” to the component and not propagate up to the parent components.

Thanks

Josh
Former Community Manager
May 26, 2023

Might need a little more context on how you have everything structured but you should be able to specify which nested component props show up on the parent component.

May 27, 2023

I want to show specific properties from an instance, with this I can only show ALL properties from an instance, or none.

Jeremy_Knudsen
Active Member
June 2, 2023

+1 Yes please!!

Armin_Rouhanian
Active Member
June 3, 2023

+1 No need to explain why we need this. Great idea.

Armin The Riverman
Laura_Fegan
June 9, 2023

+1 for us too