honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Paul Gschwendtner b5ab7aff43 refactor: add override keyword to members implementing abstract declarations (#42512) 
In combination with the TS `noImplicitOverride` compatibility changes,
we also want to follow the best-practice of adding `override` to
members which are implemented as part of abstract classes. This
commit fixes all instances which will be flagged as part of the
custom `no-implicit-override-abstract` TSLint rule.

PR Close #42512
2021-07-12 13:11:17 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
refactor(router): ensure compatibility with noImplicitOverride (#42512)
2021-07-12 13:11:15 -07:00
test
refactor: add override keyword to members implementing abstract declarations (#42512)
2021-07-12 13:11:17 -07:00
testing
fix(router): properly assign ExtraOptions to Router in RouterTestingModule (#39096)
2020-10-05 16:35:14 -07:00
upgrade
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
build: use api-golden tool from dev-infra for testing public API (#42688)
2021-06-30 11:43:48 -07:00
index.ts
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
karma-test-shim.js
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
karma.conf.js
build: move shims_for_IE to third_party directory (#37624)
2020-06-26 11:09:01 -07:00
package.json
feat(core): support TypeScript 4.3 (#42022)
2021-06-04 11:17:09 -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.