mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
Andrew Scott
e79e3cafec
The commit which made the `canceledNavigationResolution` property on the `Router` public did not add the corresponding configuration in the `ExtraOptions`. https://github.com/angular/angular/commit/3c6b653089837459809a370ebcaf8911c3bab9ed This was a mistake and is being corrected in this commit. We should not encourage changing the properties post-setup (i.e. `inject(Router).canceledNavigationResolution = 'computed'`). This manner of configuration makes the options non-tree shakeable because we have to keep both implementations in case the value changes at runtime. PR Close #43842
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.