iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/packages/router
History
Andrew Kushnir 4dfc3fe6a2 refactor(router): extract Router config utils to a separate file (#38229) 
This commit refactors Router package to move config utils to a separate file for better
organization and to resolve the problem with circular dependency issue.

Resolves #38212.

PR Close #38229
2020-07-27 09:49:14 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
refactor(router): extract Router config utils to a separate file (#38229)
2020-07-27 09:49:14 -07:00
test
refactor(router): extract Router config utils to a separate file (#38229)
2020-07-27 09:49:14 -07:00
testing
docs(router): fix a typo in example code (#37309)
2020-06-01 17:19:45 -04: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: provide full paths to ts_api_guardian_test_npm_package and ts_api_guardian_test (#36034)
2020-03-12 09:49:00 -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
Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495)
2020-06-10 08:21:45 -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.