mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
3817e5f1df
The `createOrReuseChildren` function calls shouldReuseRoute with the previous child values use as the future and the future child value used as the current argument. This is incosistent with the argument order in `createNode`. This inconsistent order can make it difficult/impossible to correctly implement the `shouldReuseRoute` function. Usually this order doesn't matter because simple equality checks are made on the args and it doesn't matter which is which. More detail can be found in the bug report: #16192. Fix #16192 BREAKING CHANGE: This change corrects the argument order when calling RouteReuseStrategy#shouldReuseRoute. Previously, when evaluating child routes, they would be called with the future and current arguments would be swapped. If your RouteReuseStrategy relies specifically on only the future or current snapshot state, you may need to update the shouldReuseRoute implementation's use of "future" and "current" ActivateRouteSnapshots. PR Close #26949 |
||
|---|---|---|
| .. | ||
| aot_ngsummary_test | ||
| operators | ||
| utils | ||
| apply_redirects.spec.ts | ||
| bootstrap.spec.ts | ||
| BUILD.bazel | ||
| config.spec.ts | ||
| create_router_state.spec.ts | ||
| create_url_tree.spec.ts | ||
| helpers.ts | ||
| integration.spec.ts | ||
| recognize.spec.ts | ||
| regression_integration.spec.ts | ||
| router.spec.ts | ||
| router_preloader.spec.ts | ||
| router_scroller.spec.ts | ||
| router_state.spec.ts | ||
| shared.spec.ts | ||
| spy_ng_module_factory_loader.spec.ts | ||
| url_serializer.spec.ts | ||
| url_tree.spec.ts | ||