Skip to main content

Expose/hide nested instances -> at component property level

  • September 22, 2022
  • 353 replies
  • 16840 views

Show first post

353 replies

Tom E.
  • New Participant
  • November 28, 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.

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.


ACKERMAN_LINDSAY

Running into problem right now, Need This!!


Michelle15
  • New Member
  • January 6, 2026

+1