You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
UID doesn't exist on getCurrentInstance proxy in VUE3. This results in validations being registered as _vuelidate_undefined, which causes issues with multiple validations as they are all registered as the same (thus overwriting).
$registerAs = `_vuelidate_${uid}`
Expected behavior
Validations should be registered as _vuelidate_xxxx, where xxxx is the VUE instance uid. Instead, they are registered as _vuelidate_undefined.
Additional context
This issue was introduced in this PR #1082 . From what I can see, uid exists only on the internal instance in VUE3 (which the comments in the linked PR mention wanting to avoid using).
The text was updated successfully, but these errors were encountered:
…#1090 (#1091)
* test: 🧪 test that uid are undefined in vue3
* fix(core): 🐛 uid was undefined on vue3
create our own uid to be agnostic of vue version
Co-authored-by: Florent Bouisset <florent.bouisset@jellysmack.com>
Describe the bug
UID doesn't exist on
getCurrentInstanceproxy in VUE3. This results in validations being registered as_vuelidate_undefined, which causes issues with multiple validations as they are all registered as the same (thus overwriting).Expected behavior
Validations should be registered as _vuelidate_xxxx, where xxxx is the VUE instance uid. Instead, they are registered as _vuelidate_undefined.
Additional context
This issue was introduced in this PR #1082 . From what I can see, uid exists only on the internal instance in VUE3 (which the comments in the linked PR mention wanting to avoid using).
The text was updated successfully, but these errors were encountered: