Borys Ponomarenko

it is possible to achieve the same result with built-in filters, which will syntax nicer: ```js const scoped = key => 'root.scope.' + key; const MyComponent = { filters {...

We have one use case, which might be connected to this issue, but correct me if I'm wrong. What I'm trying to achieve in an application, is to simply display...

@posva I can work on Pull Request to add router's `onAbort()` guard, if you agree about it conceptually. What do you think?

Is there any issue, ticket or rfc where progress for this feature can be tracked? I linked PR above, which seems related and can potentially solve this issue. There is...

@posva Is the changes in connected PR #3047 are related to "wait until the error naming is settled", or there is different discussion somewhere in RFC or GitHub Issue thread?

@posva You are right, this issue is about changes to `` api, while I was talking about slightly different solution which I thought would help to solve this issue as...

Alternatively, access to only `componentOptions` should be enough if `componentOptions` will have access to the parent component (like `vm.$options`). In this case it would be possible to get access to:...

@posva I understand that you are actively working on the next version of the router, and this kind of feature can significantly improve usage of the `vue-router` in more complex...

Hi @posva. Thanks for coming back on this one. > This is pretty much a duplicate of #2118. Importing the `router` instance (or the store) do not work on SSR...

> My guess is that data fetching might not belong in the routing but even with global `beforeResolve`, you can achieve code splitting because you can directly access the component...