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

Files

T

arturovt bedb257afc fix(common): cleanup URL change listeners when the root view is removed (#44901 )

The `Location` creates the `_urlChangeSubscription` when the `onUrlChange` is called for the first time.
The subscription `next` function captures `this` and prevents the `Location` from being garbage collected
when the root view is removed.

PR Close #44901

2022-02-14 14:02:26 -08:00

scripts

…

src

fix(core): input coercion (#42803 )

2022-02-07 10:52:59 -08:00

test

fix(common): cleanup URL change listeners when the root view is removed (#44901 )

2022-02-14 14:02:26 -08: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

refactor(compiler-cli): update peerDependencies to require rxjs ^7.4.0 (#43748 )

2021-10-06 15:57:59 -07: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