You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Guard
true
false
@angular/router
navigate to route
stop navigation
angular-routing
navigate to route
navigate to fallback route
The text was updated successfully, but these errors were encountered:
meeroslav
changed the title
[Feat] Add route unregister
[Feat] Add route guards
Nov 2, 2020
meeroslav
changed the title
[Feat] Add route guards
[Feat] Enable route guards
Nov 2, 2020
meeroslav
added a commit
to meeroslav/angular-routing
that referenced
this issue
Nov 2, 2020
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/router
canActivate
:The text was updated successfully, but these errors were encountered: