I am glad when it came to "not reusable" the first two things I thought of off the top of my head was v-bind, or make a functional component that just rams those values in.. And then 2 seconds later, you specify them both... So, I am glad I am thinking 'the vue way'
Bro that last one where we can use tailwind I don't not even know exists. Now i can postpone learning css animations and stick to tailwind. Thanks bro.
Sir, we have a existed vue app which one was written on "Option API" Now we want to transfer it into "Composition API", is there any easy way to transfer it or we have to write it from scratch. [Your reply is very important]
to be honest, the way you'll migrate depends on the rest of app. one approach for extremely incremental changes would be using the Composition API with a setup function and moving things there over time. Then, once a component is completely refactored to the setup function - you can convert it to .
To be honest, if it works, just let it be. There is nothing wrong with using Options API. I recommend create new components in Composition API, if you really want to use Composition API. Composition API will require you to switch to other patterns (mixins will not work anymore) and you ended up refactoring most of your apps.
@@SecondKing_2K Yes, but sometimes overwriting can be counter-productive and can take a lot of time :) IMO, If the components can be rewrite with using composables function, then yes. Otherwise just leave it like that :) Me personally i have been rewriting some apps to Composition API, because i can use some neat trick. But otherwise there is nothing wrong with Options API.
