skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
16.2.x
angular__angular/packages/router
T
History
Andrew Scott b79b4aca91 fix(router): RouterTestingHarness should throw if a component is expected but navigation fails (#52357) 
The `RouterTestingHarness` should throw an error if the call to `navigateByUrl`
expects a component to be activated but the navigation failed.

fixes #52344

PR Close #52357
2023-10-25 11:04:24 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
docs(router): add clarification for behavior of paramsInheritanceStrategy: 'emptyOnly' (#52170)
2023-10-13 11:14:22 +02:00
test
refactor(router): Have router subscribe to transition events to update state (#48427)
2023-08-22 08:04:01 -07:00
testing
fix(router): RouterTestingHarness should throw if a component is expected but navigation fails (#52357)
2023-10-25 11:04:24 -07:00
upgrade
docs(router): Make links out of @see tags (#50110)
2023-06-14 10:54:38 +02:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
build(bazel): create AIO example playgrounds for manual testing
2022-11-22 13:51:16 -07:00
index.ts
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
package.json
build: update minimum supported Node version from 16.13.0 -> 16.14.0 (#49771)
2023-04-11 07:56:31 -07:00
PACKAGE.md
docs: add package doc files (#26047)
2018-10-05 15:42:14 -07:00
public_api.ts
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
README.md
docs(router): remove obsolete sections in README.md (#27880)
2019-01-11 11:15:59 -08:00

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.

Reference in New Issue View Git Blame Copy Permalink