Expose/hide nested instances -> at component property level

+1 .. still waiting for this feature! 

+1 as well, this needs to be on the roadmap!

+1 
new to the whole workflow but after starting to set up systems I ran into this problem very quickly.

Having a concept of “private” and “public” properties could help, similar to the way using a dot or underscore at the start of component names hides the component from publishing. Only “public” ones would appear to consumers of the library.

At the moment I’m having to sacrifice some of the usefulness of my unpublished nested components by reducing properties in order to prevent too many from appearing.

This is a highly wanted feature! The components we make in our design system gets way to complex for the users of design system to understand when all of the nested props (that they not should touch) need to be displayed – when f.ex. only one of them is needed to be exposed in the main component. Hope ypu will prioritize to fix this soon! Waiting for this for years should not be necessary.

+1 for this also. Maybe prefixing the prop with _ or .

+1 for my team too! 

This is a big bugbare of mine. It’s severely holding up how we make components within our design system.

We have core components such as Cards that house content with replaceable body content. This suggested feature is desirable for instances where we want the content inside to be exposed as editable children, but we don’t want the card itself to have its variants changed.

+1 What can I say – essential for a complex design system (to make it less complex for its users).

+1, why does this functionality not exist yet?