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 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?
+1 It would make so much more sense to be able to swap variants in the property panel instead of having to revert back to creating multiple components
I’m also wondering if it would be possible to swap instances without having to publish the component you’re swapping. In the example @Paul_Brouwer posted above, ideally I wouldn’t want the status component to be published but I would want users to be able to switch the status of the component nonetheless. Dunno if that makes a lot of sense ^^’
Now with the instance swap property, you have to publish all the components that you use for the swap and since we can’t use variants for it, we’re back to publishing more components rather than less…
Not having to publish components makes sense, but I think it limits your sources of truth. If you have many different variants, including this pill, that need to be changed, then you must manually change them everywhere.
ah but they would still be linked to the original component in the library, so if you update the pill in the library then it updates everywhere… but yeah then it needs to be published and not hidden… arh always the struggle to keep it light but useful, but low maintenance ^^’
I also think this change is necessary. The new updates on the components are great, ie the boolean properties, but it’s very limited if it doesn’t allow us to easily acces variants. Having to click again on the layer defeats the whole point of the boolean property.
