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.

389 replies

JGKIDD
Apr 24, 2023 1:19 PM UTC

Bumping! This would really elevate design systems

Florian_Ruee
Apr 25, 2023 9:10 PM UTC

+1 ! Would be game changer 🥰

StefanieP
Apr 27, 2023 10:36 AM UTC

+1000 please! 🙏

kendrick
Apr 27, 2023 5:08 PM UTC

+1

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

Apr 28, 2023 2:57 AM UTC

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

Ash.Sharifi
Apr 28, 2023 8:08 AM UTC

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
Apr 30, 2023 11:31 PM UTC

Yes please, this feature is required.

Matthew_Vella
May 3, 2023 2:52 PM UTC

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
May 9, 2023 8:25 PM UTC

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

Maxime_Rodier
May 17, 2023 8:04 AM UTC

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