Abdelrahman Awad

@bodograumann I thought about that initially, but aside from how hard is it to find a new name, I think it is better to build on the existing popularity of...

@ux-engineer I already use `vue-demi` for another lib (villus) which works fine there, however for `vee-validate` it will be tricky as a large portion of the code base depends on...

@KuenzelIT Yes it's only for Vue 3, it's in the readme at moment but I guess I need to add a more clear banner on top or something.

@runxc1 Many changes in Vue 3 internals actually break v3, there was no way the API would remain the same. The upside is that we have a much better API...

@walfly > Can you release a version of vee-validate that has the old api and runs in the vue3? Well, that's the impossible part, Vue 3 changed lots of the...

At the moment there is no other way, typically when a locale is changed you probably need to change a few things as well like the URL or the direction...

I will have to think about this, but generally you can work around this by using the composition API and passing the errors ref to the parent component using `provide/inject`.

Not really. I probably missed it. Feel free to PR it on the `v3` branch

Can you create an example for this? I just tried a 2.7.8 installation and it works fine against the snippet provided.

This might be intended if you didn't call `useField` for that field name. Mainly because `validateField` tries to search for the field instance in the form: https://github.com/logaretm/vee-validate/blob/main/packages/vee-validate/src/useForm.ts#L481-L486 The `validate` method...