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

Summary


Let's look at all the operations of the Angular router one more time:

When the browser is loading /inbox/33/messages/44(popup:compose), the router will do the following. First, it will apply redirects. In this example, none of them will be applied, and the URL will stay as is. Then the router will use this URL to construct a new router state:

Next, the router will instantiate the conversation and message components:

Now, let's say the message component has the following link in its template:

<a [routerLink]="[{outlets: {popup: ['message', this.id]}}]">Edit</a>

The router link directive will take the array and will set the href attribute to

/inbox/33/messages/44(popup:message/44). Now, the user triggers a navigation by clicking on the link. The router will take the constructed URL and start the process all over again: it will find that the conversation and message components are already in place. So no work is needed there. But it will create an instance of PopupMessageCmp...