Option to expose or hide nested component properties

+1
I really want this as well. I usually build my components with breakpoints that are linked to responsive collection that contains modes for breakpoints. These breakpoint properties is not something my designers need to see in the panel. They are just noise. 

I hope this hasn’t been forgotten! 

+1x1000

+1

I need this soooo badly! 

Yes!!!    +1,000,000

We are trying to create efficiency and consistency by using nested components, but, displaying all of their properties is not necessary and can create clutter and confusión.

+1000!

This would make my life so much easier to be able to quickly see only properties that are necessary. It definitely slows down my work because I have to look through all properties, every time.

when can this happen please!

+1 — this becomes a real problem when working with production-level design systems.

Right now, exposing nested properties is all-or-nothing, which forces us to surface a lot of implementation details that should stay internal. In many cases, we only want to expose a very limited set of controls (e.g. icon swap or a single boolean), while keeping layout, size, or internal variants locked.

As a result:

• the properties panel becomes cluttered
• components are easier to misuse
• abstraction breaks down, especially for less experienced designers

This is not just about convenience — it directly impacts the quality and scalability of a design system.

Selective control over which nested properties are exposed would solve this cleanly and make component APIs much more predictable.

+1

I really hope this is taken into consideration.
I lead a design system, we work with the atomic design methodology, as most people do.
I prefer to nest small components within larger components and patterns.
I could list many scenarios I’ve come across but a simple example is I have a heading component (H1-H4) and I don’t need the H1 variant to be an option in components that wouldn’t use it i.e. side drawer, popover, banner etc.

The designers using the design system aren’t always savvy with heading rules so removing this option would mean way less human error.