f9497bf28b
Prior to this change, if a navigation was ongoing and a new one came in, the router could get into a state where `router.currentNavigation` was `null` even though a navigation was executing. This change moves where we set the `currentNavigation` value so it's inside a `switchMap`. This solves the problem because the `finally` on the `switchMap` had been setting `currentNavigation` to `null` but the new `currentNavigation` value would have already been set. Essentially this was a timing problem and is resolved with this change. Fixes #29389 #29590 PR Close #29636 |
||
---|---|---|
.. | ||
aot_ngsummary_test | ||
operators | ||
utils | ||
BUILD.bazel | ||
apply_redirects.spec.ts | ||
bootstrap.spec.ts | ||
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 |