mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
7f16902a72
Prior to the change to support defining required segments before and after the wildcard, the meaning of the wildcard path was '0 or more' so path: foo with a child of ** will still match the ** route when the URL is only 'foo'. If developers want to _require_ something, they can still use path: foo/:anyRequired/**/bar |
||
|---|---|---|
| .. | ||
| 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.