mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
This commit adds the ability to directly abort a navigation through the `Router.getCurrentNavigation()?.abort()` method. While there are no feature requests for this, it is a feature that will be necessary for integration with the navigation API. The API enables better tracking of an ongoing navigation for SPAs and a site visitor can cancel a navigation by clicking the stop button in the browser. While this could technically be done on the transition with an internal jsdoc comment to hide it from application developers, there's no need. With this feature, I believe it would be possible to create somewhat of a shim to integrate with the navigation API even before the router has full support using the router events to control a deferred navigation that never commits the URL and always aborts itself on navigation end. PR Close #60380 |
||
|---|---|---|
| .. | ||
| 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.