mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
Andrew Scott
000363eec5
There are two functions which do the same thing and are meant to search for the closest loaded config in the `ActivatedRouteSnapshot` parent tree. These can be combined to reduce code duplication. One difference in the current implementation is the early exit for the implementation in `activate_routes` when `route.component` is defined. This early exit takes advantage of the fact that the component must then also have a `RouterOutlet`, which injects `ComponentFactoryResolver`, which would end up being the same one as what would be found if we continued to look up the parent tree. This is only a tiny optimization that will actually break when we add `providers` as a feature to the `Route` config. In this scenario, we _must_ find the correct injector in the parent routes and cannot rely on a parent `RouterOutlet` since there may be some route with a providers list in between. PR Close #45613
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.