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.
I think I understand the problem why they still don’t make it now:
Because they are nested instance, they can always be swapped. So if Figma had the ability to deselect unwanted nested properties from the original parent instance, then what would happen to the swapped nested instance. Would they also be configured like the original, or have full set of its properties?
Or if there were a feature to lock the instance from being swapped, this would make more sense.
Even if it prevented instance swaps, it could still solve a lot of cases, especially if variant-based swaps were still allowed.
It could also work by whitelisting property names to expose (as opposed to blacklisting properties to hide) - then any swapped component that has those same property names would expose them. But I suppose it wouldn’t be as clean as hiding/exposing based on property ID.
Running into problem right now, Need This!!
+1
+1
this. hopefully they are working on this. Really running into a wall. Have tried so many workarounds, figma just breaks.
Adding my vote for this feature. I’m going to have to brief all my users on which properties they should edit, and which they have to leave alone. I can predict with 99.9% certainty that they won’t remember, and will get themselves into a right old mess….. 🙄
Hey all, PM responsible for Component Props. Just wanted to say totally hear the desires and needs for this feature, and it’s something we intend to build at some point. Right now other DS-related features are ahead in priority for us, but part of those priorities do include updates to component props. This is not a forgotten part of the product - were still doing active development here.
Hi
Maybe for Config 2026? (or sooner would be cool!)
Thanks 🙏
+1
If this feature was ever to be added it would be cool to add the same functionality into the “instance swap” → “Preferred instances” flow. Currently that feature just drops the default component instance in place of the slot, which is not always the desired outcome.
e.g I might want to have a user switch between the slot, and an icon only secondary button. Too bad if thats not the default config, I have to ‘expose nested instances’ loosing intentionality and control.
+1
+1. Sketch was doing this 10 years ago, and it was so great.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.