@Figma came on, do something

Tbh I don’t think they’ll do anything. Not if all the admins turn a blind eye to this. They go out of their way to changes things here and there just because, things that no one ask for except their bored product designers, but they absolutely ignore what users truly want when it’s hard.

Hard things are lame. What’s cool is trying to prove you’re good at ux designing. Apparently good ux is letting users get use to one behavior, let them form muscle memories, let them do things out of habit, then proceed to change how things work out of nowhere, without any surveys beforehand. Wait for several months for users to finally figure things out on their own and come to terms with new changes, they repeat the whole process again.

What if instead of having an AI design a weather app for me, I could choose which properties of a nested component I surface to consuming designers, helping to prevent errors and drastically improving quality of life? Wouldn’t that be crazy?!

Absolutely necessary +1

I was shocked to learn today that this important feature isn’t yet supported. It’s definitely preventing me from setting up intuitive but powerful components that our team can use without overriding properties that should be locked.

+1000! This would be so helpful 🙏

@Figma Any updates on this one?

This feature would be a huge quality of life improvement and would streamline the structure of a bunch of our components while making them easier for consuming designers to use. Please @figma_support tell us you’re at least exploring how to make this feature work

+1000… 👌t2:

This feature would be highly practical. I’ve been struggling with this for a while, especially when trying to declutter complex components and streamline their usability. It would greatly enhance the workflow and component organization. Please prioritize adding this functionality soon! 🙏🏼

this feature will change and improve the quality of the design and design system. it will make it easier for us to work with complex components.

Please tell us some good news and put this one as a high priority.

Users after more than two years desperately needing this: 🤷🏼‍♂️

Figma: 🦗🦗🦗

Yes please!  I often make based components that I reuse in other instances, and I don’t always want the properties for that base component to show up in nested instances.  This would make it less confusing to use, and clean up the sidebar.

+1. With complex system, it would be great the limit the number of props exposed on these components, especially nested instances.