honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Alex Eagle ef534c0cc1 build: upgrade bazel rules to latest (#20768) 
Add enough BUILD files to make it possible to
`bazel build packages/core/test`

Also re-format BUILD.bazel files with Buildifier.
Add a CI lint check that they stay formatted.

PR Close #20768
 		2017-12-07 11:27:50 -08:00
..
scripts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
src fix: Update test code to type-check under TS 2.5 (#20175) 2017-11-15 18:12:16 -06:00
test fix(router): 'merge' queryParamHandling strategy should be able to remove query params (#19733) 2017-11-14 11:01:04 -08:00
testing build: upgrade bazel rules to latest (#20768) 2017-12-07 11:27:50 -08:00
upgrade refactor: make all rollup config ES5 compatible (#20028) 2017-10-30 23:09:17 -04:00
.gitignore refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
BUILD.bazel build: upgrade bazel rules to latest (#20768) 2017-12-07 11:27:50 -08:00
LICENSE refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
README.md refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
index.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
karma-test-shim.js test(router): enable running the campaign in non-ES6 browsers 2017-04-10 15:43:42 -07:00
karma.conf.js build: build modules and examples for karma 2017-03-08 17:35:20 -08:00
package.json build: update to rxjs@5.5.0 (#19345) 2017-10-18 11:17:43 -07:00
public_api.ts build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00
rollup.config.js fix: add missing globals from each rollup configuration (#20028) 2017-10-30 23:09:17 -04:00
tsconfig-build.json build: remove references to `tsc-wrapped` (#19298) 2017-09-21 13:55:52 -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