Skip to main content
Zoltan_Szalay
Sep 22, 2022 1:44 PM UTC

Expose/hide nested instances -> at component property level

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.

387 replies

Bjorn_Witte
New Participant
Sep 22, 2022 2:03 PM UTC

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

Lea_Delazer1
Sep 27, 2022 11:16 AM UTC

+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
Sep 28, 2022 3:22 PM UTC

+1, is really needed!

0xtutti
New Member
Oct 1, 2022 8:27 AM UTC

+1, this is really needed.

hummh
Active Member
Oct 12, 2022 12:39 PM UTC

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
New Member
Oct 12, 2022 12:46 PM UTC

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
Oct 27, 2022 5:12 PM UTC

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

andy4
Nov 1, 2022 5:43 PM UTC

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
New Participant
Nov 11, 2022 4:31 PM UTC

+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
New Participant
Nov 17, 2022 2:48 PM UTC

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