TypeError on Safari: Attempted to assign to readonly property, pointing to setDirty function about vee-validate HOT 5 CLOSED

The last release used a Proxy object to assign those flags, but we dropped it because of this here #42

I think the next release should be able to fix it, you can pull the repo and build the latest changes and test it if you would like. Hopefully I can release a tag today or tomorrow. Thanks for the feedback!

from vee-validate.

Whoops, my mistakes. Next branch solve the problems. Thank you so much.

from vee-validate.

Thank you so much @logaretm for fast response. Actually, Proxy problem was occurred previously, but it was solved by adding proxy-polyfills (https://github.com/GoogleChrome/proxy-polyfill).
I tried to pull the latest changes, and yes, there is no Proxy usage compare to latest release. However, an error appear as shown in figure below, at line 2259. I've tried to find value/object contained in 'this'. Actually, 'this' was undefined.


Looking for next release, thanks for great works. Embeddeding laravel validation is such a great idea.

from vee-validate.

I always liked Laravel's validation. You probably built the Vue 1.0 version which is located at master branch, you need to checkout the next branch which should contain Vue 2.0 stuff.

from vee-validate.

No problem, I probably should have made it more clearer in the readme.

from vee-validate.