-
Now that Vue officially supports the composition API is it possible for Vee Validate 4.0 to support Vue 2.7.x? That would make migrating from Vue 2 to Vue 3 much easier. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Ya, this has been a huge headache. My other third-party libraries made their existing apis work with vue 3. Then made major changes after the fact in the next version making the upgrade fairly painless. This one, if you want to use vue 3 you've got to completely rewrite your validation code. |
Beta Was this translation helpful? Give feedback.
-
I'm not sure since I haven't checked if Vue 2.7 has the same VNode API which was the main reason for the breaking change. The old API wasn't possible with Vue 3 so v4 had to be something different, unfortunately. Now even if If you are curious to know the reason specifically. In Vue 3, the VNode API doesn't tell you which node has |
Beta Was this translation helpful? Give feedback.
-
@dparish / @logaretm Did you end up figuring out which version of vee-validate is the correct one to use to be compatible with Vue 2 and Vue 3 versions at the same time, while doing a safe upgrade? |
Beta Was this translation helpful? Give feedback.
I'm not sure since I haven't checked if Vue 2.7 has the same VNode API which was the main reason for the breaking change. The old API wasn't possible with Vue 3 so v4 had to be something different, unfortunately.
Now even if
2.7
worked with v4, I don't see that helping your migration efforts (well maybe if you want to slowly migrate to Vue 3) as you will still need to change your validation API. But the opposite like @tinyfly mentioned would be if it was possible.If you are curious to know the reason specifically. In Vue 3, the VNode API doesn't tell you which node has
v-model
on it as directives were converted to functions and event handlers. So that means theValidationProvider
won't b…