iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/packages/router
History
Tobias Bosch ce1d7c4a6e refactor: use view engine also for NgModuleFactorys (#16658) 
* refactor(core): provide error message in stack for reflective DI

Fixes #16355

* fix(compiler): make AOT work with `noUnusedParameters`

Fixes #15532

* refactor: use view engine also for `NgModuleFactory`s

This is a prerequisite for being able to mock providers
in AOTed code later on.
2017-05-11 10:26:02 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
docs(router): Change CanDeactivate to CanLoad (#16237)
2017-05-10 16:34:34 -07:00
test
refactor: use view engine also for NgModuleFactorys (#16658)
2017-05-11 10:26:02 -07:00
testing
fix(router): Update types for TypeScript nullability support
2017-04-18 12:07:33 -07:00
upgrade
fix(router): forward the query parameters in the ng1 -> ng2 url sync (#16249)
2017-04-24 12:13:47 -05:00
.gitignore
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
LICENSE
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
package.json
build: fix paths to typings files so tsickle resolves imports correctly
2017-03-16 17:34:29 -07:00
public_api.ts
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
rollup.config.js
test: add systemjs+umd integration test (#14196)
2017-03-19 12:23:07 -05:00
tsconfig-build.json
fix(router): Update types for TypeScript nullability support
2017-04-18 12:07:33 -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