frontend migration to vue3 #5121
Description
Plan to upgrade to vue3:
We already have a playground for vue3 in #4456
But that we also make some steps in the direction of vue3, here my proposal for a plan.
- 1. Add eslint rules for vue3, that we don't add new deprecated things, and can solve them step by step
-
2. Fix them@BacLuc went as far as he was allowed - 3. Replace svg integration, because our current svg integration does not work with vue3 frontend: replace vite-plugin-vue2-svg with vite-plugin-svg4vue #5173
- 4. (Look if we can already use the vue3 compatible version of hal-json-vuex). Maybe finish the following PR
- 5. ... do other small steps we can already do
- use tailwind for utility classes
- break down global.scss into different categories (vuetify class overrides, utility classes, html default style overrides, ecamp specific global classes)
- change form components from options API to composition API
- 6. Switch to vue3 with a big bang, as soon as the calendar is ready
I have made a fork where we can run vue3 and vue2 alongside and are not bothered by the updates for the new frontend when we try new things for the vue3 frontend.
https://github.com/BacLuc/ecamp3-vue3/
And here is a branch where i found all the places we need to switch from @import to @use in scss:
https://github.com/BacLuc/ecamp3/tree/prepare-scss-vue3
Metadata
Metadata
Assignees
Labels
No labels