Skip to main content
Zoltan_Szalay
September 22, 2022

Expose/hide nested instances -> at component property level

  • September 22, 2022
  • 381 replies
  • 20388 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

Active Member
November 13, 2023

This is really important to make nested components usable…

Want to add another important point in this regard:

🆕 Make the exposed properties addable to the main component so they can be sorted manually in between the original components properties (distinguishable by a small icon/dot/whatever).

Yuval_Burton
November 20, 2023

I like this idea as well. The workaround for me was breaking variants into separate components to prevent user error when using nested instances.

Claire_Durrant
New Member
November 22, 2023

Desperately want this please!!

Krister_D
New Member
November 23, 2023

This would be really helpful. @Mel_Bosch and @Brian_Heston are spot on.

Please give this to us 🥺

Daniel_Bolyhos
November 23, 2023

+1

A must have!

Dan_Hopewell
Active Member
November 28, 2023

Another vote in favor of this capability. It would be a huge unlock in terms of balancing the power/scalability of a design system with its usability.

A current (and relatively simple) use case:

I’m building a card component that includes multiple nested button components.

I’d love to be able to expose to end users of the card component certain of the nested button components’ properties that they’ll need access to (e.g., button state variants, text property, icon swap property) while restricting/locking down other properties that would only serve to break the layout, mess up the intended hierarchy or otherwise break consistency guidelines (e.g., button size and style variants).

VCM
November 30, 2023

+1

Indispensable!!

Dan_Hopewell
Active Member
December 1, 2023

Coincidentally, I just watched this presentation by Nathan Curtis from Schema 2022 in which, almost as an aside starting at the 14:14 mark, he briefly makes the case for this as a need along with a related/alternative feature idea (“forwarding” property values from a main component to its nested instances):

And maybe in the future (wink-wink, Figma) we can get to the point where we aren’t just exposing nested instances, but exposing properties within exposed nested instances. And being able to maybe forward properties from something bigger to something smaller, so that our consumers of the design system, when they’re working with a bigger unit, aren’t overwhelmed by having to configure and align all of their different knobs they’re trying to tune.

December 1, 2023

+1
Really really needed!

Matthew_Vella
December 4, 2023

+1 lets do it