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.
This would be amazing!! When could we get this on the roadmap? Another +1 from me.
It’s been 2 years now. Cannot let this die. Please Figma, we’re in dire need of this!
Can you let us know if this is being worked upon, its been 2 years and would be an incredibly powerful addition, and would reduce mistakes by end users.
🫠 is this on the roadmap?
+1 this would help tremendously!
+1 I’m in need of this for years at this point.
+1. God, please.
The total lack of acknowledgement in spite of this many votes over 2+ years is disappointing yet unsurprising.
+1 , this would clean up our components greatly - disappointed it’s not possible! Also, no answer in two years?!
Hello. Figma team, any news on this? Framer does it in a very simple way: select the nested layer and create a property at the parent component level; do this and remove the add property/nested components, as makes no sense at nested component level… Also with Framer approach, you could set a property that controls both parent and nested component layers/elements…
+1, just had today a huge frustration about this, please solve it as soon as you can.
thank you in advance.
Just moved from Sketch to Figma and I am very disappointed this feature doesn’t exist. Sketch supports this along with a few other features that I would consider more basic for components. Please add this ASAP
+1 we have the same problem, we can’t seem to align our props to code due to this restriction.
+1 here-- choosing which properties to expose, and the ORDER that they show up, would solve so many problems for us
+1, this would be incredibly powerful for my team!
Totally +1, we need this feature! <3
Such a needed feature, can’t wait for this to happen !
+1, would love this feature!
+1 I need this this option
+1 This is truly a must have!
+1 pleaaaaase this is causing a lot of messy component making just to make things consistent between code and Figma.
+1, 2 years on and this feature is still sought after? This would be so helpful when implemented
+1 this is an essential feature
+1 Added my vote to the post! We need this!
Why do something really worthwhile, it’s better to spend time developing the thickness of the strikethrough?))
The request is more than two years old.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
