honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Filipe Silva 26a8c5961e fix(router): support NgFactory promise in loadChildren typings (#29392) 
The router loadChildren property already supports a promise that returns a NgModuleFactory, but the typings cause the compilation to fail.

PR Close #29392
2019-03-25 09:30:28 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
fix(router): support NgFactory promise in loadChildren typings (#29392)
2019-03-25 09:30:28 -07:00
test
build(bazel): fix router test failure (#29375)
2019-03-19 23:39:37 -04:00
testing
build: turn off dts bundling for packages that still are not supported (#29128)
2019-03-07 10:47:20 -08:00
upgrade
build: turn off dts bundling for packages that still are not supported (#29128)
2019-03-07 10:47:20 -08: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 to rxjs@6.0.0 (#23679)
2018-05-03 10:53:39 -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
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.

Guide

Read the dev guide here.