Thorsten Lünborg
Thorsten Lünborg
I would like to re-open this, but so far, I only have you saying "it's flashing, and that's wrong". Without a reproduction / demo, I can't verify that it's a...
I understand your confusion, but if you look at the documentation closesly, it states that passing a callback to `next()` is only necessary (and supported) in `beforeRouteEnter`, because we can't...
You might have a point there, I'll reopen #1676 for further discussion, because that ticket was apprearantly requesting that change as well and is newer.
No difference, really. I just feel that bdoms has made a good case that should at least be discussed. I'm not convinced yet if offering a callback for all in-component...
Oh... it's realy time for bed for me.
Hi Brad. just thinking out loud: I think this won't be so easy to do since those two things - the scrollposition the router saves right now, and the scrollpostion...
> Hold it for now - I believe this should be considered a bug and is fixable. @yyx990803 For camelCase it mighr be, i think i even have an open...
Saving a reactive proxy to `chrome.storage` is likely troublesome as well: https://github.com/vuejs/vue-next/issues/3423 Snippet from the repo linked in that issue (in case it might get deleted) ```js // this.errorinfo is...
I don't think it's a problem with the linter. The linter is right, `props` is not being used, the instance proxy property is being used instead. And for that, we...