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

Vue 2 EOL - focus on oruga-next #496

Closed
mlmoravek opened this issue Mar 4, 2023 · 2 comments · Fixed by #662
Closed

Vue 2 EOL - focus on oruga-next #496

mlmoravek opened this issue Mar 4, 2023 · 2 comments · Fixed by #662
Labels
breaking Breaking changes

Comments

@mlmoravek
Copy link
Member

Through the announcement of the EOL for vue 2 (https://v2.vuejs.org/lts/) i suggest to focus on improving oruga-next (vue 3) and make oruga (vue 2) legacy.

I really like the idea of a component library which is detached from a css framework. The ecosystem for vue 3 is getting very well and I think it's time to finish up oruga before it gets leftover. Focusing on oruga-next and dropping oruga for vue 2 could bring some time savings and faster development.

What's your opinion about that?

@jtommy
Copy link
Member

jtommy commented Mar 4, 2023

I agree with you, totally!

Next breaking release will be the last of oruga for Vue 2

@mlmoravek
Copy link
Member Author

Nice! Is there also some intend to switch from options api to composition api and use some more modern common practises like composables?

@mlmoravek mlmoravek added the breaking Breaking changes label Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants