Instance properties do not behave as I would expect.
Instead of forcing me to create multiple components in order to swap instances, I would prefer swapping variables.
As an example, I have a progress bar component with multiple variants set to 10%, 20%, 30% and so on. As it stands, swapping the instance would make me have 11 different components that could all be one variant.
It’s simply not intuitive to swap variants from the child level while clearly properties are meant to give parent level control over components.
I just experienced the same problem; having a component set with variants just doesn’t let me switch it on parent level component…
How the heck didn’t they see this coming?
I have the same pain of not being able to select a Variant as an instance instead of a separate component.
My screenshot is a simplified example of the situation. The whole project uses a large library of icons, assembled by a set of variants. I don’t want to break it down into separate components to get the flexibility of working with icons through an instance swap. But I like the Instance swap function at all, if only there was a way to choose a Variant…
You wrote “Instead of forcing me to create multiple components in order to swap instances, I would prefer swapping variables.”
I’am in a similar situation where i have to decide what to do with my common assets (icons, logos): Do multiple components or just one with multiple variants. Which is the better method? Why do you choose the “multiple variants in 1 component” way?