Expose/hide nested instances -> at component property level

Forum|Forum|4 years ago
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.

Show previous replies

JGKIDD

Bumping! This would really elevate design systems

Florian_Ruee

+1 ! Would be game changer 🥰

StefanieP

+1000 please! 🙏

kendrick

+1

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

A

alfee

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

Ash.Sharifi

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.

Mike_Trilford

Yes please, this feature is required.

Matthew_Vella

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.