mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
3ec9ee65b9
No test was added for this case because I can't think of a test case to write that would work. This change updates the code for a consistent mental model of setting the `browserUrlTree`. It's only meant to track the `UrlTree` that the `UrlHandlingStrategy` is set to extract, not the full `rawUrl`. Notice that everywhere else, the `browserUrlTree` is set to `urlAfterRedirects`, which is computed based on the extracted URL, _not_ the `rawUrl`. PR Close #43426 |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| test | ||
| testing | ||
| upgrade | ||
| .gitignore | ||
| BUILD.bazel | ||
| index.ts | ||
| karma-test-shim.js | ||
| karma.conf.js | ||
| 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.