-
Notifications
You must be signed in to change notification settings - Fork 41
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
Upgrade to Vue 3 #350
Comments
Hi team, I have to tell I already looked at this last year as this was some sort of natural follow-up of migrating to the latest From a completely personal point of view, I'm not looking at it for now neither because After some reading though, it seems there can be a possibility to upgrade For the rest, as @chrismayer said, we should be able to stay with the |
in Vue 3 it is possible to store state like a map in composables or with the "official" state management library "pinia" |
For sharing the map state across components in Vue 3, I find composables quite useful. |
Since "Vue 2 will reach End of Life (EOL) on December 31st, 2023" (see https://v2.vuejs.org/lts/) we should tackle the upgrade of the code base to Vue 3. Even tough offering different new concepts in Vue 3 one could stay at the classic component approach of Vue 2. So the upgrade effort should be OK besides the normal upgrade madness, but no complete re-write.
The text was updated successfully, but these errors were encountered: