-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Migration to Vue 3 #2689
Migration to Vue 3 #2689
Conversation
Replace vuex with pinia Fix some routing issues Fix most vue3 breaking changes
Remove garbage from vscode renaming Fix reading route in pinia store
Replace moment with dayjs Fix some routing issues Fix some vuex store leftovers
Add turkey to the list Detect ro, nl-be, is locales
Implements #2623 |
I like it and I want to perhaps join in on this. But what is the plan / to do list. Also do we want to perhaps consider moving to typescript (improved tooling). Let me know how I can join in |
Thanks for ur interest, my current plan for this migration is to port the current codebase to Vue3 with only mostly necessary changes before we reach the EOL of Vue2. The tasks left on my todo list are:
Ur more than welcome to help out in any of those tasks or lmk if u find anything that seems wrong. |
Okay good to know. I'll build upon your branch and try to move everything over to composition api and typescript. Lovely to hear that almost everything is ported to Vue3. |
Just checked about noty. I almost exclusively use my own notification system using just pinia. Will try to make a semi compatible port from noty :D |
I just looked into this and found vue-toastification to have everything we need and added it so u dont have to bother with this. |
@kloon15 Branch is now aligned with master again, I pulled the most recent updates as well and should be ready for merge. |
Thank you very much i will test it this week! |
@kloon15 I've done some light testing and there seems to be a bug with the prompts. For ( I suspect this is due to Pinia running state mutations async but not confirmed yet. |
|
Will test it further this weekend to confirm why it's happening on my side |
Realign with master and add new features
This looks good to me, ill change it to ready to review. Thanks everyone for their contribs! |
You all have done a great job! |
@kloon15 Hi,The Vue3 version is likely related to the code in the "VideoPlayer.vue" file, which cannot play MKV format video files. |
The thing is, most browsers dont even support the mkv container, let alone the proprietary codecs such files are encoded with.
Whats ur use case that requires u to play mkv in a browser? |
You can test this file, which could be played online in the previous version of the file browser. https://www.daji.it:66/release/v2.5.1/test.mkv Actually, what I mean is that all the MKV files I have been using could be played normally in the browser before. |
We could bypass videojs for unsupported formats i guess. Dont have a better idea. |
This migration to vue3 broke the ability to pull down to refresh on mobile in a text editor. I assume |
Brings the frontend to run under Vue 3 while maintaining the same behavior as much as possible.
Current status: rewrite to typescript and compositions API mostly finished.
🚨 Before submitting your PR, please read community, and indicate which issues (in any of the repos) are either fixed or closed by this PR. See GitHub Help: Closing issues using keywords.