-
Notifications
You must be signed in to change notification settings - Fork 275
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
Proposal of breaking changes in 2.x #103
Comments
Hi guys. Keep up the code work on this tool, it's definitly very useful ! |
Hey @clemjlt, thanks a lot for your support! |
Awesome, I didn't realize you deployed that feature in V1. release, as you mentioned it was supposed to be packed with the V2. Anyway, thanks ! :) |
Hi @HZooly, Anu update on Vue3 Support for the vue-tour package? Really looking forward to it. Our application vue3 upgrade is almost done except for the migration of this package. Thanks for all the work. |
Hello! |
Hi, @HZooly. Happy new year :-) . Any update on this. |
Hi, A v2.x has been released! It's not compatible with Vue 3 yet (the Vue 3 will probably be vue-tour v3.x) but we have shipped two breaking changes:
Our focus is now entirely on the Vue 3 version. |
Hi @mmorainville , any expected date for Vue3 support. |
Changes
Vue 3
We plan to update Vue to version 3 in order to use the new slot API.
Constant naming conventions
We will replace constants in
/src/shared/constants.js
syntax from uppercase to camel case to be more conventional.VTour options refactor
Plan to pass all VTour and VStep options in a single object.
Rename stop label
Buttons labels are configurable, enabled buttons too. We will rename
stopButton
byfinishButton
in/src/shared/constants.js
.Upgrade to Popper v2
In order to fix some placement issues, improve package bundle size, and get better performances, Vue Tour 2.0 will work with Popper v2.
Proposals
If you have any idea for vue-tour v2.x, feel free to comment this issue.
The text was updated successfully, but these errors were encountered: