Angular Router: Paths, Wildcards, and Redirections | CodeSignal Learn

Angular Router: Paths, Wildcards, and Redirections | CodeSignal Learn

Introduction

Welcome to the second lesson of the "Front-end Engineering in Angular" course! In this lesson, we will explore the Angular Router, a powerful tool that allows you to navigate between different views or components in an Angular application. Understanding routing is essential for creating dynamic and user-friendly web applications. Let's dive into how we can define routes, handle undefined paths, and implement redirections to enhance user navigation. 🚀

Defining Basic Routes

To start, let's learn how to set up basic routes in an Angular application. Routes are defined in a configuration array, where each route is an object with properties like path and component . This configuration is typically placed in app.routes.ts . Here's a simple example: TypeScript import { Routes } from '@angular/router'; import { UsersComponent } from './users/users.component'; export const routes: Routes = [{ path: 'users', component: UsersComponent }]; In this example, we define a route with the path'users' that loads the UsersComponent . This basic setup allows users to navigate to the UsersComponent by visiting the /users URL. It's important to note that the routes array is processed from top to bottom, and the first match is used, so the order of routes can affect navigation.

Using Wildcards for Undefined Routes

Next, let's handle undefined routes using wildcards. Wildcards are useful for creating a 404 page that informs users when they try to access a non-existent route. Here's how you can implement a wildcard route: export const routes: Routes = [{ path: 'users', component: UsersComponent }, { path: '**', component: PageNotFoundComponent } // Wildcard route for a 404 page]; In this code snippet, the path: '**' acts as a catch-all for any undefined routes. If a user navigates to a path that doesn't match any defined routes, the PageNotFoundComponent is displayed, providing a user-friendly 404 page. Because Angular checks each route in the array sequentially and stops at the first match it finds, more specific routes should be placed before wildcard or catch-all routes to prevent unintended matches. For example, if a wildcard route ({ path: '**', component: PageNotFoundComponent }) is placed before other routes, it will catch all navigation attempts, making other routes unreachable.

Sign up

Join the 1M+ learners on CodeSignal

Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal

Implementing Redirections

Redirections are useful for guiding users to specific routes, such as setting a default route or handling legacy URLs. Let's see how to implement a simple redirection: export const routes: Routes = [{ path: 'users', component: UsersComponent }, { path: '', redirectTo: '/users', pathMatch: 'full' }]; In this example, the empty path'' is redirected to /users . The pathMatch: 'full' ensures that the entire URL path is matched before redirecting. This setup is helpful for directing users to a default route when they visit the root URL of your application. If pathMatch: 'full' is not specified, Angular assumes pathMatch: 'prefix', meaning the router will match any URL that starts with the specified path. For example: export const routes: Routes = [{ path: '', redirectTo: '/users' } // Without pathMatch: 'full' { path: 'users', component: UsersComponent },]; This would create an infinite redirect loop if another route starts with / (like /users), as Angular would match any URL that begins with ''. Using pathMatch: 'full' ensures that the redirection only occurs when the full path exactly matches '' (the root).

Navigating with routerLink

In Angular templates, you can use the routerLink directive to navigate between routes. This is preferred over traditional anchor tags (<a>) because routerLink works seamlessly with Angular's routing system, allowing for client-side navigation without reloading the page. Here's an example: <a routerLink="/users">Go to Users</a> Using routerLink ensures that the Angular router handles the navigation, providing a smoother user experience compared to a simple link that would cause a full page reload.

Comprehensive Code Example

Now, let's put it all together in a comprehensive example that includes paths, wildcards, and redirections. This will help you see how these elements work together to create a seamless navigation experience: export const routes: Routes = [{ path: 'users', component: UsersComponent }, { path: '', redirectTo: '/users', pathMatch: 'full' }, { path: '**', component: PageNotFoundComponent }]; In this complete example, we have defined a route for the UsersComponent, set up a redirection from the root path to /users, and included a wildcard route for handling undefined paths. This configuration ensures that users are directed to the appropriate components and receive a helpful 404 page when needed.

TypeScript

export const routes: Routes = [
  { path: 'users', component: UsersComponent },
  { path: '', redirectTo: '/users', pathMatch: 'full' },
  { path: '**', component: PageNotFoundComponent }
];