-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate from Vue 2 to Vue 3 #64
Comments
We can take inspiration from nextcloud/spreed#9448 for a less bumpy upgrade path and changes we can do while staying on Vue 2.7. |
nextcloud/calendar-availability-vue does not need adjustments for Vue 3 accoring to @GVodyanov. Removing it from the list of affected components. |
Item broken down into chunks. @GVodyanov please assign yourself to the ticket of the store you're tackling :) nextcloud/calendar#5685 would be a good first migration. It's the smallest store we have. |
Migrating to pinia is not a bad idea, but certainly not required for a migration to vue 3. Tasks works just fine with vue 3 and vuex 4 and the adjustments to the store required to make it work with vue 3 are quite small. See nextcloud/tasks#1971 as well. |
We will pause this epic a bit. |
Describe the task
https://v3-migration.vuejs.org/
Exemplary migration: nextcloud/spreed#9448
Affected components
Calendar,
Calendar Resource Management, Contacts, Mail, Calendar-availability-vuePreparation
::v-deep
to:deep
) calendar#5693::v-deep
to:deep
) contacts#3786::v-deep
to:deep
) mail#9242::v-deep
to:deep
) calendar-availability-vue#212Upgrades
To do
to be defined
The text was updated successfully, but these errors were encountered: