Closed vesper8 closed 6 years ago
I made an example repo with instructions on how to reproduce this
All details in this comment: https://github.com/matfish2/vue-tables-2/issues/339#issuecomment-347777669
I've ran into this same error when using vuex-router-sync
, it seems it has to do with the destroyed hook/watches, if I used vuex without the router sync (or don't call sync on them) it won't trigger the error.
I was able to make it go away by adding another check for the presence of $el
, on index.js
:
if (this == this.$root && this.$el) {
this.$el.outerHTML = this.$originalEl;
}
Not sure of the implications of this ? I'm still hooking up the whole spa so I'm not sure it introduces some erratic behaviour but it does seem to be working as expected otherwise.
thank you @mnussbaumer I just tried this and it does indeed make the ugly red error go away with no noticeable side-effects.. I do also wonder what are the implications of this.. could @jeffreyguenther comment on this? If this seems like a safe thing to do then maybe a PR would be accepted to add it?
Awesome, that probably is something we should have been doing from the beginning.
I just cut a release for 2.0.1 with this fix in it.
I'm running into this error where if I have a very simple basic table from https://github.com/matfish2/vue-tables-2 on a page, if I go to another page and click back, or if I just click a link that reloads the same page, I get the errors below.
The rest of my app works fine with turbolinks/vue-turbolinks
I do use vue on every page. I'm using the latest 2.0 version of vue-turbolinks
I noticed this error only happens with https://github.com/matfish2/vue-tables-2 but also only happens if I'm using the "vuex" mode for the server-side tables. If I switch off vuex, then I don't get the error.. I'm pretty confused what's causing it but my app depends on using vuex server tables so hopefully you can give me some help fixing this problem
thanks!