honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/modules/@angular/router
History
Victor Berchet 31a7709ece test: execute router tests on .`/test.sh browser` (#10053) 2016-07-21 16:12:40 -07:00
..
scripts chore(router): changes the router setup to align with other modules 2016-06-21 12:17:30 -07:00
src fix(router): routerLinkActive should only set classes after the router has successfully navigated 2016-07-20 17:51:21 -07:00
test fix(router): routerLinkActive should only set classes after the router has successfully navigated 2016-07-20 17:51:21 -07:00
testing fix(router): routerLinkActive should only set classes after the router has successfully navigated 2016-07-20 17:51:21 -07:00
.gitignore chore(router): update config before publishing to npm 2016-06-21 12:17:30 -07:00
CHANGELOG.md chore(router): bump up version number 2016-06-30 14:58:59 -07:00
LICENSE chore: set up test and build infrastructure 2016-06-21 12:17:30 -07:00
README.md chore(README): fix a typo 2016-06-21 12:17:30 -07:00
index.ts fix(router): export navigation extras 2016-07-18 17:42:04 -07:00
karma-test-shim.js refactor(core): clean up platform bootstrap and initTestEnvironment 2016-07-08 13:41:38 -07:00
karma.conf.js test: execute router tests on .`/test.sh browser` (#10053) 2016-07-21 16:12:40 -07:00
package.json chore(router): bump up version number 2016-06-30 14:58:59 -07:00
rollup.config.js fix(router): fix rollup config to properly set up rxjs 2016-07-15 16:27:54 -07:00
testing.ts refactor(router): rename RouterTestModule into RouterTestingModule 2016-07-20 11:39:31 -07:00
tsconfig-es5.json fix(router): routerLinkActive should only set classes after the router has successfully navigated 2016-07-20 17:51:21 -07:00
tsconfig-es2015.json fix(router): routerLinkActive should only set classes after the router has successfully navigated 2016-07-20 17:51:21 -07:00
tsconfig.json cleanup(router): removes unnecessary files from tsconfig 2016-07-20 11:44:07 -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.

Overview

Read the overview of the Router here.

Guide

Read the dev guide here.