-
Notifications
You must be signed in to change notification settings - Fork 96
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
[Question] Why not Vue 3? #17
Comments
That's a fair question, thanks! I think we mainly focused on Getting Things Done™, instead of checking whether all the dependencies (vuetify, chartjs) would work with Vue 3. But we could totally migrate to Vue 3 in the future 👍 |
Oh, ok, cool then.. Also, I think with all the libraries used, only vuetify lacks Vue 3 support, so i'll probably use something like tailwindcss instead. |
@AnoRebel that would be awesome 👍 |
Sorry it took I while, I was kinda busy.. |
Just FYI: Vuetify3 is not getting released soon. We have to hold our breath for months, if it continues like this with Vuetify 3 😉 This UI does not use Typescript (sadly), no vee-validate (luckily) and also not vue-class-components (luckily). That will save you lots of migration efforts! My Vue2 + Vuetify2 project: https://github.com/fdm-monster/fdm-monster/tree/develop/client-vue You can ping me here for questions, if you like. |
As the heading suggests, this is more of a question than an issue.
Why not use vue 3?
Is it because of Vuetify(since it doesnt have a vue 3 integration yet)?
The text was updated successfully, but these errors were encountered: