mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
Andrew Scott
4d2e006372
Currently, the `Router` will create the `EnvironmentInjector` for a `Route` with `providers` as soon as it _attempts_ to match segments to the `Route`. Instead, this change updates the logic to only create the injector once we have confirmed that the `Route` matches. Note that this will include partial matches where the final navigation still fails with a "cannot match any routes to segment" error. We need to maintain the injector hierarchy so we still need to create parent injectors before descending into the child routes and determining if there is a full match or just a partial one. resolves #45988 PR Close #45990
Angular Router
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, we often want to split applications into multiple bundles and load them on demand. Doing this transparently isn’t trivial.
The Angular router is designed to solve these problems. Using the router, you can declaratively specify application state, manage state transitions while taking care of the URL, and load components on demand.
Guide
Read the dev guide here.