Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

useVuelidate breaks reactivity connection of object returned by a toRefs

See original GitHub issue

The codesandbox won’t compile due to some error with vue-demi, but I hope you can get the gist. Providing an object obtained via toRefs into useVuelidate will break the connection between the original state and the generated refs. Was pretty painful to debug.

If the refs object is denstructured, everything works as expected. I tried to look into the source code, but could not understand where the problem lies

https://codesandbox.io/s/brave-raman-fex90?file=/src/App.vue

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

dobromir-hristovcommented, Feb 18, 2021

Yeah… We have the main ways working, so I think that’s good for now

0reactions

IlCallocommented, Feb 18, 2021

I see, I was reading there instead: https://vuelidate-next.netlify.app/advanced_usage.html#composition-api But I see you just updated that page too to show the reactive state usage.

The highlighted problem still holds btw, but I guess it’s intended behaviour or we’re in “won’t fix” realm