honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/modules/@angular/router
History
Ferdinand Malcher d55f747858 docs(router): attribute notation for string paths (#12205) 
Either bind an expression or use the attribute notation.
The mixed way `[routerLink]="/path"` won't work.
Prefer the attribute notation for string-only paths
 		2016-10-17 22:53:55 -07:00
..
scripts chore(router): changes the router setup to align with other modules 2016-06-21 12:17:30 -07:00
src docs(router): attribute notation for string paths (#12205) 2016-10-17 22:53:55 -07:00
test fix(router): improve error message (#12102) 2016-10-06 15:19:22 -07:00
testing docs(RouterTestingModule) change modules to imports in example (#12118) 2016-10-06 10:22:39 -07: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 chore: set up test and build infrastructure 2016-06-21 12:17:30 -07:00
README.md refactor(core): change module semantics 2016-07-26 07:04:10 -07:00
index.ts fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
karma-test-shim.js refactor: add license header to JS files & format files (#12081) 2016-10-04 20:39:20 -07: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: update descriptions in package.jsons 2016-09-14 16:44:39 -07:00
rollup-testing.config.js refactor: add license header to JS files & format files (#12081) 2016-10-04 20:39:20 -07:00
rollup.config.js refactor: add license header to JS files & format files (#12081) 2016-10-04 20:39:20 -07:00
tsconfig-build.json fix(build): prevent package tsconfigs from shadowing main tsconfig (#11454) 2016-09-08 15:01:22 -07:00
tsconfig-testing.json fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -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.

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