Currently all routeView binding handlers have a dependency on activeRoutes, so during a transition, that is bulk replaced, causing the entire tree to re-render. A transition at depth 3 to another sibling should not cause depth 1 and 2 to rerender. We need to do deep comparisons before attempting to call component.init.
Also in general there may be resolve promises that are resolved already, but will still be async and resolve on the next tick - flickering over to route-loading during that time is a bad experience. This might be solved with the solution to the above problem.
nathanboktae
commented
9 years ago
Currently all
routeViewbinding handlers have a dependency onactiveRoutes, so during a transition, that is bulk replaced, causing the entire tree to re-render. A transition at depth 3 to another sibling should not cause depth 1 and 2 to rerender. We need to do deep comparisons before attempting to callcomponent.init.Also in general there may be
resolvepromises that are resolved already, but will still be async and resolve on the next tick - flickering over toroute-loadingduring that time is a bad experience. This might be solved with the solution to the above problem.