mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
d966fdd438
`RouterOutlet` components can initialize _during_ change detection (for example, if they exist in an embedded view). When this happens, data from the router should be bound immediately to the routed components rather than not being available until the next round of change detection. This is mostly just a problem for testing because change detection is triggered manually. It would be surprising to have to detect changes _twice_ on the fixture in order to get data bound to the routed component. PR Close #49741 |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| test | ||
| testing | ||
| upgrade | ||
| .gitignore | ||
| BUILD.bazel | ||
| index.ts | ||
| package.json | ||
| PACKAGE.md | ||
| public_api.ts | ||
| README.md | ||
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.