honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Joey Perrott 698b0288be build: reformat repo to new clang@1.4.0 (#36613) 
PR Close #36613
 		2020-04-14 12:08:36 -07:00
..
scripts
…
src build: reformat repo to new clang@1.4.0 (#36613) 2020-04-14 12:08:36 -07:00
test build: reformat repo to new clang@1.4.0 (#36613) 2020-04-14 12:08:36 -07:00
testing build: reformat repo to new clang@1.4.0 (#36613) 2020-04-14 12:08:36 -07:00
upgrade build: reformat repo to new clang@1.4.0 (#36613) 2020-04-14 12:08:36 -07:00
.gitignore
…
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
PACKAGE.md docs: add package doc files (#26047) 2018-10-05 15:42:14 -07:00
README.md docs(router): remove obsolete sections in README.md (#27880) 2019-01-11 11:15:59 -08:00
index.ts
…
karma-test-shim.js build: reformat repo to new clang@1.4.0 (#36613) 2020-04-14 12:08:36 -07:00
karma.conf.js build: reference zone.js from source directly instead of npm. (#33046) 2019-11-06 00:48:34 +00:00
package.json build(packaging): add repository.directory field to package.jsons (#27544) 2020-02-25 13:12:45 -08:00
public_api.ts build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07: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.