Skip to content
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

Migrate from Vue 2 to Vue 3 #156

Open
The4thLaw opened this issue Feb 6, 2023 · 0 comments
Open

Migrate from Vue 2 to Vue 3 #156

The4thLaw opened this issue Feb 6, 2023 · 0 comments
Labels
impact:behind the scenes Issues that users would probably never notice prio:low type:enhancement
Milestone

Comments

@The4thLaw
Copy link
Owner

The4thLaw commented Feb 6, 2023

Summary
Vue 2 will only be supported until end of 2023. We should migrate to Vue 3 now that most libraries have been adapted.

Documentation links

Points of attention

  • Vuetify must be migrated at the same time. We must check that all components we need are supported (not all v2 components are supported in v3 at the time this issue is created)

Alternatives
Some components are no longer supported. An alternative must be found.

Potentially useful tools

@The4thLaw The4thLaw added type:enhancement impact:behind the scenes Issues that users would probably never notice prio:low labels Feb 6, 2023
@The4thLaw The4thLaw added this to the v3.2.0 milestone Feb 6, 2023
@The4thLaw The4thLaw modified the milestones: v3.2.0, v3.3.0 Feb 14, 2024
The4thLaw added a commit that referenced this issue Mar 14, 2024
- Vue 3 with compat, start of createApp usage
- Start of Vuetify 3
- Start of Router
- Start of vue-i18n
...

Refs #156
The4thLaw added a commit that referenced this issue Mar 15, 2024
Also fixed issues with the Stylelint configuration.

Refs #156
The4thLaw added a commit that referenced this issue Mar 15, 2024
The4thLaw added a commit that referenced this issue Mar 15, 2024
The4thLaw added a commit that referenced this issue Mar 15, 2024
The4thLaw added a commit that referenced this issue Mar 15, 2024
This will prevent boring vue-i18n warning messages.

Refs #156
The4thLaw added a commit that referenced this issue Mar 15, 2024
The4thLaw added a commit that referenced this issue Mar 15, 2024
The4thLaw added a commit that referenced this issue Mar 16, 2024
The4thLaw added a commit that referenced this issue Mar 16, 2024
Also cleaned up old Vue 2 code.

Refs #156
The4thLaw added a commit that referenced this issue Mar 19, 2024
Fixes colors, pagination styling (without an ugly hack from v2), change of field L&F in Vuetify 3.

Refs #156
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
Refs #156
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
- Fixed the menu
- Fixed overrides not working due to some elements being rendered outside of the app root
- Fixed light theme detection
- Fixed search field alignment and look
- Fixed overlay and removed hacks
- Fixed search results showing as a clickable card
- Fixed footer size and color
- Removed pagination hack

Refs #156
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
The4thLaw added a commit that referenced this issue Mar 19, 2024
Moved to the composition API to ease access to the slots. Must still be tested with other things than tags.

Refs #156
The4thLaw added a commit that referenced this issue Mar 28, 2024
No longer supported in non-legacy vue-i18n.

Refs #156
The4thLaw added a commit that referenced this issue Mar 28, 2024
The4thLaw added a commit that referenced this issue Aug 22, 2024
The4thLaw added a commit that referenced this issue Aug 23, 2024
The4thLaw added a commit that referenced this issue Sep 5, 2024
The4thLaw added a commit that referenced this issue Sep 8, 2024
The4thLaw added a commit that referenced this issue Sep 9, 2024
The4thLaw added a commit that referenced this issue Sep 9, 2024
The4thLaw added a commit that referenced this issue Sep 9, 2024
Remove all manual imports.

Refs #156
The4thLaw added a commit that referenced this issue Sep 11, 2024
Not ideal, but it will have to do for now.

Refs #156
The4thLaw added a commit that referenced this issue Sep 11, 2024
@The4thLaw The4thLaw modified the milestones: v3.3.0, v3.1.0 Sep 12, 2024
The4thLaw added a commit that referenced this issue Sep 13, 2024
The4thLaw added a commit that referenced this issue Sep 13, 2024
The4thLaw added a commit that referenced this issue Sep 13, 2024
The4thLaw added a commit that referenced this issue Sep 13, 2024
The4thLaw added a commit that referenced this issue Sep 22, 2024
The4thLaw added a commit that referenced this issue Sep 22, 2024
The4thLaw added a commit that referenced this issue Sep 25, 2024
The4thLaw added a commit that referenced this issue Sep 25, 2024
@The4thLaw The4thLaw modified the milestones: v3.2.0, v3.1.0 Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:behind the scenes Issues that users would probably never notice prio:low type:enhancement
Projects
None yet
Development

No branches or pull requests

1 participant