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
At some point in my component I wanted to do this:
exportconst{methods: {mymethod(){this.$options.data// Does not raise errorconstoriginalData=this.$options.data()// TypeError: this.$options is undefined}},}
I checked the console and this.$options.data gets overwritten by vue-async-computed to be vueAsyncComputedInjectedDataFn, and the error is in this line:
However, I think this problem should be fixed from vue-async-computed's side, not from the developer side. As I understand, the Vue API allows us to simply call this.$options.data()
The text was updated successfully, but these errors were encountered:
At some point in my component I wanted to do this:
I checked the console and
this.$options.data
gets overwritten by vue-async-computed to bevueAsyncComputedInjectedDataFn
, and the error is in this line:In my component, this solves the error:
However, I think this problem should be fixed from vue-async-computed's side, not from the developer side. As I understand, the Vue API allows us to simply call
this.$options.data()
The text was updated successfully, but these errors were encountered: