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

Support @vue/compat + VeeValidate v2 #4379

Closed
bedus-creation opened this issue Jul 20, 2023 · 1 comment
Closed

Support @vue/compat + VeeValidate v2 #4379

bedus-creation opened this issue Jul 20, 2023 · 1 comment

Comments

@bedus-creation
Copy link

Is your feature request related to a problem? Please describe.

We have a very big project and we use vue:

Vue v2.7.x
VeeValidate v2.x

We are planning to migrate our project to vue3.

  • We are thinking @vue/compat to migrate from vue 2.x to 3.x

But now, we stuck, because seems vee validate v2 is not compatible with @vue/compat

Describe the solution you'd like

Are there any possibilities, that vee validate v3 will become compatible with @vue/compat ?

@bedus-creation bedus-creation changed the title Support @vue/compat + VeeValidate v3 Support @vue/compat + VeeValidate v2 Jul 20, 2023
@logaretm
Copy link
Owner

logaretm commented Jul 20, 2023

Sorry, this is not an issue and I have addressed it in older issues.

vee-validate v2/v3 API will never work with Vue 3.0, it relied on VDOM and VNode API which was drastically changed in Vue 2 -> 3. So there is no way to backport this.

This is listed in the "Known limitations" section of @vue/compat

Dependencies that rely on Vue 2 internal APIs or undocumented behavior. The most common case is usage of private properties on VNodes. If your project relies on component libraries like Vuetify, Quasar or ElementUI, it is best to wait for their Vue 3 compatible versions.

I understand this may not be ideal for you, but there is nothing I can do about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants