Any update on this ?

Please Figma, just copy paste and ship this please. Zoltan already did the work for you 🙏

Love that properties from nested components are available.

Unfortunately when designing object oriented components it becomes a huge pain to see many unnecessary properties that should remain untouched. Also creates clutter.

Curious what the Figma team thinks the best solution is.

I guess what we need is a setting for each property of a component to allow it to be listed or not in parent components.

But maybe there are better ways. I trust them to come up with something brilliant.

+1, we need this 🙏

Honestly, cant wait to have this feature, this is such a drawback for a big design system!

+1 this is a blocker for our team to establish functional product templates to increase production. This would create a massive amount of efficiency for our team.

Would really help to have this for more complex patterns that I’m adding in to our design system also.

+1 - I have several instances where this would clean up the sidebar for designers and improve the usability of complex components.

+1 - This is something we really need

This is a must-have feature for any large-scale design system with multiple designers. We need ways to lock down permutations of nested components to avoid user error.

I think it would be really helpful, if there is a way to hide properties. I need this in a lot of complex components. Right now i have to trust the designer, that they don’t use single nested instances wrong.

+1 thanks for reporting this! we need it too.

+1 This is currently preventing my team from adopting this feature for our design system and this would be a HUGE improvement

+1 we need it ! the sooner the better 💪

➕ 1️⃣ this will grately improve component composition

I can’t upvote this enough. The current component model forces many hacky workarounds to approach something usable, and at best there’s some other tradeoff or invalid configuration you’ve had to expose.

This is the root of most of these problems. We need to be able to compose larger components from smaller ones, while hiding some of the implementation details of the smaller ones. This include hiding properties, changing the “recommended” instance swaps, or even limiting the instance swaps allowed.

Yes, please! 🙏

Our team is working on a new design system and it’d make things so much easier if there was a way to hide specific props of nested components depending on where they are used. Otherwise, the props panel can grow unwieldy pretty fast and it would make so much sense to tailor exposed props to the specific use case.

@Figma-Team: Could you share if you’re even considering such a feature? It would really help us to decide basic questions regarding our component structure. Thank you!

+1 YES 1000 Times!

+1 This is critical to avoid overwhelming designers with too much irrelevant choice

This is an absolute necessity. Figma really needs to prioritize this feature.

💯 Everything already said 324x ☝️

Hell yes to this

It’s must fix the issue. Long-due request.

We are also building out of design system, and I can concur that this would be super helpful to make the components easier to use and handle when creating mocks.

It could be as simple as a eye toggle so you can choose what to hide and what to show.