Rangle.io : Angular Training
Search…
Introduction
License
Why Angular?
The Architect's Guide to Angular
EcmaScript 6 and TypeScript Features
The JavaScript Toolchain
Bootstrapping an Angular Application
Components in Angular
Directives
Advanced Components
Observables
Angular Dependency Injection
Http
Change Detection
Zone.js
Advanced Angular
What is Immutability
Pipes
Forms
Modules
Routing
Why Routing?
Configuring Routes
Redirecting the Router to Another Route
Defining Links Between Routes
Dynamically Adding Route Components
Using Route Parameters
Defining Child Routes
Controlling Access to or from a Route
Passing Optional Parameters to a Route
Using Auxiliary Routes
State Management
TDD Testing
Migrating AngularJS Projects to Angular
Project Setup
Angular CLI
Accessibility in Angular
Internationalization in Angular
Glossary
Further Reading And Reference
Powered By GitBook
Why Routing?
Routing allows us to express some aspects of the application's state in the URL. Unlike with server-side front-end solutions, this is optional - we can build the full application without ever changing the URL. Adding routing, however, allows the user to go straight into certain aspects of the application. This is very convenient as it can keep your application linkable and bookmarkable and allow users to share links with others.
Routing allows you to:
  • Maintain the state of the application
  • Implement modular applications
  • Implement the application based on the roles (certain roles have access to certain URLs)
Previous
Routing
Next
Configuring Routes
Last modified 3yr ago
Copy link