Skip to main content

Expose/hide nested instances -> at component property level


Show first post

300 replies

Preston_Booth

This would be amazing!! When could we get this on the roadmap? Another +1 from me.


ThuyAnh
  • New Participant
  • 12 replies
  • October 2, 2024

It’s been 2 years now. Cannot let this die. Please Figma, we’re in dire need of this!


Andy14
  • New Member
  • 3 replies
  • October 2, 2024

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.


Seamus_Leonard2

🫠 is this on the roadmap?


Jessie_Hunter

+1 this would help tremendously!


Julius_Klaus

+1 I’m in need of this for years at this point.


ari3
  • 8 replies
  • October 15, 2024

+1. God, please.

The total lack of acknowledgement in spite of this many votes over 2+ years is disappointing yet unsurprising.


Gilbert
  • 2 replies
  • October 18, 2024

+1 , this would clean up our components greatly - disappointed it’s not possible! Also, no answer in two years?!


Alex_Carvalho

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…


Zsolt_Nagy

+1, just had today a huge frustration about this, please solve it as soon as you can.

thank you in advance.


Kathleen_Lawless

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


ange1sha
  • 11 replies
  • October 28, 2024

Jeena
  • 1 reply
  • October 29, 2024

+1 we have the same problem, we can’t seem to align our props to code due to this restriction.


r_sh
  • Active Member
  • 25 replies
  • October 31, 2024

+1 here-- choosing which properties to expose, and the ORDER that they show up, would solve so many problems for us


Vicky_Huang

+1, this would be incredibly powerful for my team!


Aleksandra_Grochowska_UX_UI

Totally +1, we need this feature! <3


Mathieu13
  • 1 reply
  • November 7, 2024

Such a needed feature, can’t wait for this to happen !


Anne_Stoer

+1, would love this feature!


James_Grubb

+1 I need this this option


Erik_Wetendorf

+1 This is truly a must have!


Autumn_Dawe-Baillie

+1 pleaaaaase this is causing a lot of messy component making just to make things consistent between code and Figma.


Hywel_Jenkins

+1, 2 years on and this feature is still sought after? This would be so helpful when implemented


Nick_Ekste

+1 this is an essential feature


Evie_Zhang1

+1 Added my vote to the post! We need this!


Sergey47
  • 1 reply
  • November 26, 2024

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.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings