angular-cn/packages/router
kevinphelps ed0cf7e2cb fix(router): set href when routerLink is used on an 'area' element (#28441)
closes #28401

PR Close #28441
2019-02-05 23:28:40 -05:00
..
scripts
src fix(router): set href when routerLink is used on an 'area' element (#28441) 2019-02-05 23:28:40 -05:00
test fix(router): set href when routerLink is used on an 'area' element (#28441) 2019-02-05 23:28:40 -05:00
testing build: set a default module_name for ts_library rules (#28051) 2019-01-18 10:16:39 -08:00
upgrade build: set a default module_name for ts_library rules (#28051) 2019-01-18 10:16:39 -08:00
.gitignore
BUILD.bazel build: run offline_compiler_test using bazel (#28191) 2019-01-28 20:07:22 -08:00
PACKAGE.md
README.md docs(router): remove obsolete sections in README.md (#27880) 2019-01-11 11:15:59 -08:00
index.ts
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
public_api.ts
rollup.config.js
tsconfig-build.json

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 isnt 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.