iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/modules/@angular/router
History
vsavkin 42c89b1b9b docs(router): add a README to include a link to the guide 2016-06-21 12:17:30 -07:00
..
src fix(router): typo in starts with slash validation error 2016-06-21 12:17:30 -07:00
test fix(router): change serialize not to require parenthesis in query string to be encoded 2016-06-21 12:17:30 -07:00
tools chore(router): update config before publishing to npm 2016-06-21 12:17:30 -07:00
.clang-format chore: add lint and clang-format 2016-06-21 12:17:30 -07:00
.gitignore chore(router): update config before publishing to npm 2016-06-21 12:17:30 -07:00
CHANGELOG.md fix(router): change serialize not to require parenthesis in query string to be encoded 2016-06-21 12:17:30 -07:00
LICENSE chore: set up test and build infrastructure 2016-06-21 12:17:30 -07:00
README.md docs(router): add a README to include a link to the guide 2016-06-21 12:17:30 -07:00
index.js chore(router): update config before publishing to npm 2016-06-21 12:17:30 -07:00
karma-test-shim.js chore: set up test and build infrastructure 2016-06-21 12:17:30 -07:00
karma.conf.js chore(router): change karma reporter 2016-06-21 12:17:30 -07:00
package.json fix(router): change postinstall hook to devsetup to not require having 'typings' installed 2016-06-21 12:17:30 -07:00
tsconfig.json feat(router): add route config validation 2016-06-21 12:17:30 -07:00
tsconfig.publish.es5.json cleanup(router): enable noImplicitAny and noImplicntReturns 2016-06-21 12:17:30 -07:00
tsconfig.publish.esm.json cleanup(router): enable noImplicitAny and noImplicntReturns 2016-06-21 12:17:30 -07:00
tslint.json cleanup(router): fix tslint errors 2016-06-21 12:17:30 -07:00
typings.json chore(router): update config before publishing to npm 2016-06-21 12:17:30 -07:00

README.md

Angular Route

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.

Overview

Read the overview of the Router here.

Guide

Read the dev guide here.