iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/packages/router
History
Alex Eagle 337b6fe003 build: remove unreferenced tsconfig-build.json files (#30858) 
These are no longer needed since Bazel generates a tsconfig for each compilation

PR Close #30858
2019-06-05 09:03:36 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
fix(router): type cast correctly for IE 11 bug breaking URL Unification when comparing objects (#30464)
2019-05-15 14:09:53 -07:00
test
fix(core): require 'static' flag on queries in typings (#30639)
2019-05-24 16:55:00 -04:00
testing
build: remove unreferenced tsconfig-build.json files (#30858)
2019-06-05 09:03:36 -07:00
upgrade
build: remove unreferenced tsconfig-build.json files (#30858)
2019-06-05 09:03:36 -07:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
build: turn off dts bundling for packages that still are not supported (#29128)
2019-03-07 10:47:20 -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(ivy): run router tests with ivy on CI (#27195)
2018-11-21 09:19:40 -08:00
karma.conf.js
test(ivy): run router tests with ivy on CI (#27195)
2018-11-21 09:19:40 -08:00
package.json
build: update rxjs version requirements to 6.4.0 (#30032)
2019-04-22 11:15:33 -07:00
PACKAGE.md
docs: add package doc files (#26047)
2018-10-05 15:42:14 -07:00
public_api.ts
build: publish tree of files rather than FESMs (#18541)
2017-08-31 15:34:50 -07:00
README.md
docs(router): remove obsolete sections in README.md (#27880)
2019-01-11 11:15:59 -08: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.

Guide

Read the dev guide here.