Book Image

Angular Router

By : Victor Savkin
Book Image

Angular Router

By: Victor Savkin

Overview of this book

Managing state transitions is one of the hardest parts of building applications. This is especially true on the web, where you also need to ensure that the state is reflected in the URL. In addition, you might want to split applications into multiple bundles and load them on demand. Doing this transparently isn’t easy. The Angular router solves these problems. Using the router, you can declaratively specify application states, manage state transitions while taking care of the URL, and load bundles on demand. This book is a complete description of the Angular router written by its designer. It goes far beyond a how-to-get-started guide and talks about the library in depth. The mental model, design constraints, and the subtleties of the API-everything is covered. You’ll learn in detail how to use the router in your own applications. Predominantly, you’ll understand the inner workings of the router and how you can configure it to work with any edge cases you come across in your sites. Throughout the book, you’ll see examples from real-world use in the MailApp application. You can view the full source of this application and see how the router code works to manage the state of the application and define what is visible on screen. Reading this book will give you deep insights into why the router works the way it does and will make you an Angular router expert.
Table of Contents (19 chapters)
Angular Router
Credits
About the Author
www.PacktPub.com
Customer Feedback
Preface

Custom error handler


Every navigation will either succeed, will be cancelled, or will error. There are two ways to observe this.

The router.events observable will emit:

  • NavigationStart when navigation stars

  • NavigationEnd when navigation succeeds

  • NavigationCancel when navigation is canceled

  • NavigationError when navigation fails

All of them contain the id property we can use to group the events associated with a particular navigation.

If we call router.navigate or router.navigateByUrl directly, we will get a promise that:

  • will be resolved with true if the navigation succeeds

  • will be resolved with false if the navigation gets cancelled

  • will be rejected if the navigation fails

Navigation fails when the router cannot match the URL or an exception is thrown during the navigation. Usually this indicates a bug in the application, so failing is the right strategy, but not always. We can provide a custom error handler to recover from certain errors as shown in the following code:

function treatCertainErrorsAsCancelations...