{"id":685,"date":"2023-03-22T05:00:00","date_gmt":"2023-03-22T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=685"},"modified":"2023-03-21T15:14:34","modified_gmt":"2023-03-21T22:14:34","slug":"route-guards-canactivate-canactivatechild-candeactivate","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/route-guards-canactivate-canactivatechild-candeactivate\/","title":{"rendered":"Route guards – canActivate, canActivateChild, canDeactivate"},"content":{"rendered":"\n

Yesterday, we introduced how route guards can control whether or not a user can navigate<\/a> to a new URL in our application.<\/p>\n\n\n\n

The main guard to achieve that behavior is canActivate<\/a><\/code>. This guard will run every time the user tries to access a path and only allow the user to proceed if the guard function returns true<\/code>.<\/p>\n\n\n\n

Here’s an example that’s going to check if the user is logged in before proceeding:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

If we want to redirect the user to a login component when they’re not logged in, we can do so by using the Router<\/code> service and returning a UrlTree<\/code> object as follows:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

Note how the inject function<\/a> is used in all these guards to access any service we need.<\/p>\n\n\n\n

canActivate<\/code> works well when navigating to components. If we want to prevent the lazy-loading of a child route or prevent access to any path of the child route, then canActivateChild<\/code> is what we need instead of canActivate<\/code>.<\/p>\n\n\n\n

Finally, if you want to prevent the user from navigating away from the current path\/component, you can implement the canDeactivate<\/code> guard. A typical example of such a use case is when working with complex forms where we want to make sure the user has saved their progress before navigating away from the current screen\/component:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

Another exciting feature is that we can access the current component itself instead of a service, which is especially useful for canDeactivate<\/code>:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

If you like those new framework features, I covered some more utility router functions released with Angular 14+ in this post<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Yesterday, we introduced how route guards can control whether or not a user can navigate to a new URL in our application. The main guard to achieve that behavior is canActivate. This guard will run every time the user tries to access a path and only allow the user to proceed if the guard function […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,25],"tags":[],"class_list":["post-685","post","type-post","status-publish","format-standard","hentry","category-angular","category-routing"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t