iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/packages/router
History
Patrick Shields 925e654a29 fix(router): don't use ParamsInheritanceStrategy in declarations (#21574) 
ParamsInheritanceStrategy is internal, so any references to it from the
published .d.ts files will fail.

Fixes #21456.

PR Close #21574
2018-01-23 21:34:37 -08:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
fix(router): don't use ParamsInheritanceStrategy in declarations (#21574)
2018-01-23 21:34:37 -08:00
test
build: Remove angular_src nested workspace (#21096)
2018-01-19 10:17:37 -08:00
testing
build: move repeated tsconfig attributes to a macro (#20964)
2018-01-10 12:30:19 -08:00
upgrade
Revert "feat(router): add a function set up router sync when used with downgradeModule"
2017-12-20 09:15:15 -08:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
build: move repeated tsconfig attributes to a macro (#20964)
2018-01-10 12:30:19 -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
build: add bazel test rules for remainder of packages (#21053)
2017-12-22 13:10:51 -08:00
karma.conf.js
build: build modules and examples for karma
2017-03-08 17:35:20 -08:00
LICENSE
docs(common): update copyright years (#21232)
2018-01-04 17:45:36 -05: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
README.md
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08: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