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
Alex Eagle ef32e6b0d0 fix: build and test fixes for TS 2.1 (#13294) 2017-02-08 11:32:40 -06:00
..
scripts chore(router): changes the router setup to align with other modules 2016-06-21 12:17:30 -07:00
src fix: build and test fixes for TS 2.1 (#13294) 2017-02-08 11:32:40 -06:00
test fix: build and test fixes for TS 2.1 (#13294) 2017-02-08 11:32:40 -06:00
testing chore(tslint): update tslint to 4.x (#13603) 2016-12-27 14:55:58 -08:00
.gitignore chore(router): update config before publishing to npm 2016-06-21 12:17:30 -07:00
CHANGELOG.md docs(router): add changelog for 3.0.0-rc.2 2016-08-31 16:55:18 -07:00
LICENSE style(docs): update copyright years (#13736) 2017-01-27 20:47:14 -08:00
README.md refactor(core): change module semantics 2016-07-26 07:04:10 -07:00
index.ts fix: display framework version on bootstrapped component (#13252) 2016-12-06 16:21:07 -08:00
karma-test-shim.js fix: correctly show error when karma fails to load 2017-01-06 19:30:09 -05:00
karma.conf.js refactor: add license header to JS files & format files (#12081) 2016-10-04 20:39:20 -07:00
package.json docs: branding fixes (#14132) 2017-01-27 15:03:11 -06:00
rollup-testing.config.js refactor: add license header to JS files & format files (#12081) 2016-10-04 20:39:20 -07:00
rollup-upgrade.config.js feat(router): add a provider making angular1/angular2 integration easier (#12769) 2016-11-09 13:33:33 -08:00
rollup.config.js fix(router): correctly export concatMap operator in es5 (#12430) 2016-11-02 21:55:02 -07:00
tsconfig-build.json feature(tsc-wrapped): add option for closure compiler JSDoc annotations 2016-11-18 09:37:40 -08:00
tsconfig-testing.json fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
tsconfig-upgrade.json fix(router): check if windows.console exists before using it (#12348) 2016-11-11 10:46:53 -08:00
upgrade.ts docs: branding fixes (#14132) 2017-01-27 15:03:11 -06: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.

Local development

# keep @angular/router fresh
$ ./scripts/karma.sh

# keep @angular/core fresh
$ ../../../node_modules/.bin/tsc -p modules --emitDecoratorMetadata -w

# start karma
$ ./scripts/karma.sh