Following on the FigmaConfig announcements, I played around with component properties and immediately saw the benefits to reduce the number of variants and make components more flexible.
However, it looks like I can only apply boolean properties to elements that are not components. For example, if within my card component I have a button sub-component, I’m unable to apply the boolean component to the button to show/hide it easily.
Is this a bug or by design? For us, this seems to completely defeat the purpose of booleans, given that our large components are made of many instances of smaller components.
I didn’t notice it at first either, but after a little while I realized I could do it from the icon on the right side of the Layers section.
This only works for layers, when an instance is selected the only option available is “swap instance”. Would be great if visibility on / off could be made available fpr all kinds of elements (layer / frame / group / instance).
Ooof I was wrong! It’s actually available further down, did not see t right away and tried adding it to the instance…
I agree with the OP. It’s a HUGE limitation to “component properties” if we’re not able to target layers within instances of other components used in our components. Most of our components utilize “base components” per the recommendations from Figma to help manage the structure across an entire “component set”. With this limitation, the new “component properties” would be completely useless to us.
Agreed. We need base nested components properties to work properly in component sets.
Seems like they would make those adjacent in the UI. My eye is looking for instance boolean options next to the component settings in right panel. When I look below, I see the Auto Layout section and mentally stop searching for the option. (Obviously all the new component properties features should be together, right? right??? )
Spent a good hour this morning trying to use component properties and kept running into a wall thinking that you could not use boolean and instance swap together on a component cause I didn’t see it in the UI)
Has this been reported to Figma Support? I have a bunch of objects that don’t make sense to uncomponentize in order to make them a boolean.
Yes, you describe the problem well, it’s just not visible and I also thought layer / boolean can’t be combined. Got used to it know, it’s ok but UX could be improved.
I am sure this discussion applies to my issue as well… but I am also still wondering how to apply a boolean to an existing component set as a new property??? What the heck?
I have the same problem with @Paul_Brouwer and I don’t know how to apply boolean to my components/variant. After this update, I am a bit lost from the UI perspective.