honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Jason Aden 0bf6fa5b32 fix(router): correct over-encoding of URL fragment (#22687) 
Relates to: #10280 #22337

PR Close #22687
 		2018-03-11 22:15:01 -07:00
..
scripts
…
src fix(router): correct over-encoding of URL fragment (#22687) 2018-03-11 22:15:01 -07:00
test fix(router): correct over-encoding of URL fragment (#22687) 2018-03-11 22:15:01 -07:00
testing build: add a ng_package rule for @angular/router (#22628) 2018-03-07 10:56:27 -08:00
upgrade build: add a ng_package rule for @angular/router (#22628) 2018-03-07 10:56:27 -08:00
.gitignore
…
BUILD.bazel build: add a ng_package rule for @angular/router (#22628) 2018-03-07 10:56:27 -08:00
LICENSE docs(common): update copyright years (#21232) 2018-01-04 17:45:36 -05:00
README.md
…
index.ts
…
karma-test-shim.js build: add bazel test rules for remainder of packages (#21053) 2017-12-22 13:10:51 -08:00
karma.conf.js
…
package.json feat: update tslib to 1.9.0 (#22667) 2018-03-08 16:42:34 -08:00
public_api.ts
…
rollup.config.js
…
tsconfig-build.json
…

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