Skip to main content

Expose/hide nested instances -> at component property level


Show first post

332 replies

Sveto
  • New Member
  • 1 reply
  • July 2, 2025

+1


Phu_Nguyen
  • Active Member
  • 44 replies
  • July 9, 2025

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.


Connie5
  • New Participant
  • 5 replies
  • July 11, 2025

++++


Lukas_Bruckner

+1 We really need this one


Lindsey_Drennan

I can’t believe this thread is so long with no resolution or roadmap to enable this


Apolline
  • Active Member
  • 62 replies
  • July 23, 2025

@Lindsey_Drennan Oh but 5 months ago we got this message don’t worry :)

jjcm wrote:

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.

The priority is not one of the most active thread on the forum, that should be a basic feature, no, don’t worry. It’s probably another shiny thing they can brag about on social media and during keynotes so they can say they have more features than other products.


Apolline
  • Active Member
  • 62 replies
  • July 23, 2025


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