Some thoughts on mobile front-end and single-page routing

Tree-like routing structure,

Sibling nodes can access each other,

The child node fallback key returns to the parent node,

Manage a routing footstep (the sibling node of this footstep replaces each other), and when a A, B sibling node points to the same child node C,c fallback, you can fall back to the correct parent node.

What, the page link is not changed, not good to share the address of a particular page. Have you ever seen someone send you a link and your app will automatically jump to that interface?

Question 1:

Routing state name repeat?

By Grandfather-father-son this naming method.

Some thoughts on mobile front-end and single-page routing