mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00

Files

T

Andrew Scott 1d2f5c1101 refactor(router): deprecate no longer needed resolver fields (#45597 )

DEPRECATED:

The `resolver` argument of the `RouterOutletContract.activateWith` function and the `resolver` field of the `OutletContext` class are deprecated. Passing component factory resolvers are no longer needed. The `ComponentFactoryResolver`-related symbols were deprecated in `@angular/core` package since v13.

PR Close #45597

2022-04-20 12:57:37 -07:00

scripts

…

src

refactor(router): deprecate no longer needed resolver fields (#45597 )

2022-04-20 12:57:37 -07:00

test

feat(router): Add ability to specify providers on a Route (#45673 )

2022-04-20 11:32:07 -07:00

testing

feat(router): Add Route.title with a configurable TitleStrategy (#43307 )

2022-01-27 22:02:33 +00:00

upgrade

fix(upgrade): Do not trigger duplicate navigation events from Angular Router (#43441 )

2022-02-02 19:51:20 +00:00

.gitignore

…

BUILD.bazel

build: update visibility for npm package targets to work with new integration test structure (#44238 )

2021-12-08 13:42:41 -05:00

index.ts

…

package.json

feat(core): drop support for Node.js 12 (#45286 )

2022-03-08 12:05:03 -08:00

PACKAGE.md

…

public_api.ts

…

README.md

…

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.

README.md Unescape Escape

Angular Router

Guide

README.md