Expose/hide nested instances -> at component property level

389 replies
21392 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

C

Chris67

Not showing my hover states in the variant list would be great!

Carlos_Baez

Big +1. This is necessary.

ZdenekCulik

+10. We totally needed

Daniel_Echeverri

Adding to this thread. Being able to pick which properties can be seen when using a nested instance is huge for a complex design system.

What’s interesting is you can sorta do this with the “Instance swap property” and showing “Preferred values”. This would be a similar type of idea. Showing “preferred properties” only. But in this case they couldn’t go add more properties, but even if we can just hide them that would be better than exposing all of the properties of a nested instance.

Brace

Absolutely need this.
I came here looking for this exact feature.
You can’t really build scalable, parametric design systems without this.

David_Byrne

With the new Code connect feature, we really need this now.

Our nested symbols are often broken apart to reduce the override panel for designers but we explain to the developers to re-use the nested components those styles are suppose to follow.

With the Code connect feature, we now have nested components that are already designed but don’t display that way in the component when the developers inspect the them because of breaking them apart to cater for the over ride panel.

In order to design with the atomic approach and allow developers to know which nested component instances to use from the code libraries we need the ability to remove the other overrides for the designers but still show those built nested components to the developers.

Lea.P

New Participant

This is a super necessary and important feature – and also very helpful for users!
I would be very happy about an implementation!
big +1 (or rather +100000)
🫶