We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
^3.5.13
https://stackblitz.com/edit/vitejs-vite-4umr7oj9?file=src%2FApp.vue
Run the stackblitz and open the console.
These weird proxied arrays should not be created?
With the arrayMerge option, the nested arrays are merged with proxies. Now for example a localForage can't clone the object.
Without the option, both the reactive objects are merged and they have no nested arrays with proxy.
Related issue on vuex-persist
championswimmer/vuex-persist#271 (mine)
Other users reporting the same "cannot clone error" when migrating from Vue 2 to Vue 3.
championswimmer/vuex-persist#232 championswimmer/vuex-persist#235
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Vue version
^3.5.13
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-4umr7oj9?file=src%2FApp.vue
Steps to reproduce
Run the stackblitz and open the console.
What is expected?
These weird proxied arrays should not be created?
What is actually happening?
With the arrayMerge option, the nested arrays are merged with proxies. Now for example a localForage can't clone the object.
Without the option, both the reactive objects are merged and they have no nested arrays with proxy.
System Info
Any additional comments?
Related issue on vuex-persist
championswimmer/vuex-persist#271 (mine)
Other users reporting the same "cannot clone error" when migrating from Vue 2 to Vue 3.
championswimmer/vuex-persist#232
championswimmer/vuex-persist#235
The text was updated successfully, but these errors were encountered: