angular-cn/modules/@angular/router
vsavkin 7e12208ca6 feat(router): do not support paths starting with / 2016-06-21 12:17:30 -07:00
..
src feat(router): do not support paths starting with / 2016-06-21 12:17:30 -07:00
test feat(router): do not support paths starting with / 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
LICENSE chore: set up test and build infrastructure 2016-06-21 12:17:30 -07:00
README.md docs(router): add a README 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 chore(router): bump up version number 2016-06-21 12:17:30 -07:00
tsconfig.json cleanup(router): enable noImplicitAny and noImplicntReturns 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

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 isnt 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. In this article I will discuss the API of the router, as well as the mental model and the design principles behind it.

Read the in-depth overview of the Router here.