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
The right order of the executions of callback in next() of beforeRouteEnter and mounted.
What is actually happening?
The order of the executions of callback in next() of beforeRouteEnter and mounted are different in different version of view-router Here is a reproduction link to the same sandbox with vue-router 3.4.5
The text was updated successfully, but these errors were encountered:
The behavior is still correct as one shouldn't rely on the ordering among created/mounted (component lifecycle hooks) and navigation hooks like beforeRouteEnter() because the order is not guaranteed and dependant of features like transitions, keep alive and other combinations and therefore, unreliable.
The only thing that is part of the API, and that can be made clearer in docs, is that the component renders once (DOM updates triggered) before calling the next callbacks.
Please note that the same example app has completely different behavior relates to the vue-router version. Unfortunately same thing happened in our company's application. It's a pity that the issue was closed immediately :(
Uh oh!
There was an error while loading. Please reload this page.
Version
3.4.6+
Reproduction link
https://codesandbox.io/s/vue-router-346-bgn2c
Steps to reproduce
What is expected?
The right order of the executions of callback in next() of beforeRouteEnter and mounted.
What is actually happening?
The order of the executions of callback in next() of beforeRouteEnter and mounted are different in different version of view-router
Here is a reproduction link to the same sandbox with vue-router 3.4.5
The text was updated successfully, but these errors were encountered: