-
Notifications
You must be signed in to change notification settings - Fork 136
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
Switch to Vue.js #290
Switch to Vue.js #290
Conversation
Okay, I don't want to wait any longer and there were no veto, so I'll merge this now. Any issues can be fixed in I have found two issues which I would like to be fixed until the next release:
Any ideas or PRs are welcome, @nextcloud/vue :-) |
congratulations :) Indeed, there is no veto from me, the app looks great so far! |
Congrats! Any idea when this will be included in a next release? |
There are still some issues open, that I would like to integrate in the next major release (see here: https://github.com/nextcloud/notes/milestone/9). However, I can't tell a concrete date for finishing this. |
This PR tracks the current work on switching to vuejs (see #241). There is a long way to go (the whole client-part has to be re-implemented) and for now, this reflects my first steps with vuejs, only. However, I want to be transparent, so that two people don't work on the same thing. I will make a detailed plan later and I should mention, that I'm very low on time for this. Any help is welcome, especially from experienced people.
I will update this first post in order to reflect the current state of implementation as well as the current plannings.
General
vueexample
README.md
webpack-bundle-analyzer
)Components and functionality
Router
fromvue-router
)vuex
)vue-router
)AppNavigation
fromnextcloud-vue
)Multiselect
fromnextcloud-vue
)Related Issues