mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
Set the default value of paramsInheritanceStrategy to 'always'. This change ensures that route parameters are inherited from parent routes by default, which is the behavior most users expect. It simplifies routing configuration for the majority of use cases. This change aligns Angular with other popular routing systems where child routes automatically have access to parent parameters: - React Router: useParams() includes parent params. - Vue Router: $route.params includes parent params. - Next.js: params are passed to nested layouts and pages. - TanStack Router: useParams() includes parent params with full type safety. BREAKING CHANGE: paramsInheritanceStrategy now defaults to 'always' The default value of paramsInheritanceStrategy has been changed from 'emptyOnly' to 'always'. This means that route parameters are inherited from all parent routes by default. To restore the previous behavior, set paramsInheritanceStrategy to 'emptyOnly' in your router configuration. |
||
|---|---|---|
| .. | ||
| docs | ||
| scripts | ||
| src | ||
| test | ||
| testing | ||
| upgrade | ||
| .gitignore | ||
| BUILD.bazel | ||
| index.ts | ||
| package.json | ||
| PACKAGE.md | ||
| public_api.ts | ||
| README.md | ||
| tsconfig.json | ||
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.