Really nice! One question: Is it safe in terms of performance to declare those cva classes as computed properties? On the examples that i saw on the docs, these were declared on the defineProps function, not as computed
Yes, it's safe. But if you don't want/need classes to be "recalculated" (I do) when the props change, just use a function like in the library example 👍
I think someone is in love with this CVA 😊
This is sooo goood and clean. Thank you!
where do I find the source code
Really nice! One question:
Is it safe in terms of performance to declare those cva classes as computed properties? On the examples that i saw on the docs, these were declared on the defineProps function, not as computed
Yes, it's safe.
But if you don't want/need classes to be "recalculated" (I do) when the props change, just use a function like in the library example 👍
We want more components....at the moment I see only this component on variantui
I wonder why CVA when we can bind classes as arrays and objects and mixed? I use clsx with React, but nothing in Vue.
objects & arrays are fine, I just find cva to be more readable - even more so when dealing with multiple props/variants
Yeay! Thank you
Is there a good reason to use function as a prop instead of the custom event for dismiss?
I think the best practise in Vue is to always use Event emitting.
there's good reason, can you guess why? 😃
@@cdruc Still wonder! :)
@@cdruc i think that this way it will be easier to rewrite close button to a slot
Hey, can you please the name of your font?