Skip to main content

Expose/hide nested instances -> at component property level

  • September 22, 2022
  • 353 replies
  • 16865 views

Zoltan_Szalay

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.

353 replies

Bjorn_Witte
  • New Participant
  • September 22, 2022

+1 Same Problems! We need the possibility to hide props we don’t want to export for our users.


Lea_Delazer1

+1 from me too, very much needed and it would be such a game changer in our DS. Hope this will be possible at some point!


Andreas_Falkenberg

+1, is really needed!


0xtutti
  • New Member
  • October 1, 2022

+1, this is really needed.


hummh
  • New Participant
  • October 12, 2022

Same here. The feature is a very good start, but to make it really usable it should be possible to choose which properties from nested components should be exposed / or not in a specific context. Currently it’s everything or nothing. But everything might be too much.


_Sergei_Zhukov

I agree with Harald. It is important to choose which properties from nested components should be exposed / or not in a specific context 🚀


Yaroslav_Zonov1

Same. I think it is necessary to implement this improvement, in Sketch this option worked exactly like this


andy4
  • November 1, 2022

100% this. I had this exact same thought yesterday. I’m also glad to hear that I wasn’t misremembering that this is an option in Sketch.


Harun_Alikadic1

+1 currently I am not able to use this feature in many cases because it surfaces too many options and only few are needed on the component level.


Bertrand_Fouillet1

Managing nested instance in a complex table component makes the table component itself unusable. You approach is simple and fix this issue +1


Greg_Smith
  • New Member
  • November 22, 2022

Would love the option to hide component props from consumers. For instance:

Component A

  • Nested component B
  • Nested component C

Component A is made up of two nested components, B and C. Components B and C have properties that are adjusted to provide variants of Component A. They’re really just for my use.

But if a designer “clicks in” to Component B, for instance, they can see its props, in the right sidebar (which I’ve used primarily to make those Component A variants). I don’t want them to touch the props for that nested Component B. I’d like to hide them.

I heard rumors that this might be an upcoming feature. Is this true? 🤔


Sanket_Chaudhari

+1 - need capabilities to expose selected properties from within our nested instances. Cannot use this feature without it.


Josh_Loya
  • November 27, 2022

I’m running into this limitation, too. Being able to expose properties from nested instances is the right direction, but I need to be able to selectively expose properties, rather than an all-or-nothing toggle.


Andreas_Haimerl

Would also be highly interested in this. Would make things much easier for the consumers of our enterprise Design System.


Tim_Hose
  • January 4, 2023

Replying to keep this alive. Our group would love this feature, as something like tabs or lists with nested components becomes such a massive list that they’re not usable.


sweetdrumster

Agree. It is vital to be able to mark props as private/public or simply specify which of nested components’ props should propagate to their parent.


MarcoD
  • January 24, 2023

+1, we really need this.


Adam_Przewoski

Keeping the thread alive, +1!


Namson
  • New Participant
  • February 3, 2023

We need this as well!


Erin_HG
  • New Member
  • February 8, 2023

+1 This would make exposing nested instances much more useful for my team as well.


ckeramidas
  • New Participant
  • February 8, 2023

+1, need this


+1 Please 🙏


Sarah_Proulx1

+1 exactly my problem, thank you :)!


Amanda_Bohlin1

+1 This would be so helpful!


tlapetite
  • February 23, 2023

+1, really needed for more complex design systems!