Route unregister should be called upon route destroy. Unregistering route will remove it from the routes$ and trigger navigation. This is precondition to having route guards using structural directives.
The intended behaviour is different to @angular/routercanActivate:
Route unregister should be called upon route destroy. Unregistering route will remove it from the
routes$
and trigger navigation. This is precondition to having route guards using structural directives.@angular/router
canActivate
: