vue order routing trigger guard

A flowchart of routing jumps between different components

1. Navigation is triggered (A-> B)
2. A guard in the call routing component beforeRouteLeave (to, from, next)
3. Call the global routing the front guard router.beforeEach (to, from, next)
4. B call routing exclusive guard beforeEnter (to, from.next)
5. Analytical asynchronous routing component B
6. Call routing component B in the guard beforeRouteEnter (to, from, next)
7. Call the global routing resolution guard router.beforeResolve (to, from, next)
8. Navigation is confirmed
9. Call the global routing hook router.afterEach (to, from)
10. B component rendering DOM

Multiplexing jump flowchart routing component

1. Trigger global routing hook afterEach
2. Update the DOM
3. Navigation is triggered (to change the dynamic routing parameters)
4. Call the global routing the front guard router.beforeEach (to, from, next)
5. Reuse components within the assembly to call routing guard beforeRouteUpdate (to, from, next)
6. Call the global routing resolution guard router.beforeResolve (to, from, next)
7. Navigation is confirmed
8. Call the global routing hook router, afterEach (to, from)
9. Update the DOM

Like my little partner can focus on micro-channel public number "front-end pseudo-uncle."