mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
Martin Sikora
1c11a57155
in layers Right now route static data are collected from its parents based on the logic described in `inheritedParamsDataResolve()`, merged into a single object and then merged again with merged data from resolvers. This means that a child's data can be overriden by a resolver in its parent (#34361). However, what is the expected behavior is not described in the documentation. This PR changes this behavior and merges static data and resolved data in "layers" (route by route) so child's static data and resolved data cannot be overriden by their parents. Fixes #34361 PR Close #45276
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.