iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/packages/router
History
Joey Perrott 15f8afa4bf ci: move public-api goldens to goldens directory (#35768) 
Moves the public api .d.ts files from tools/public_api_guard to
goldens/public-api.

Additionally, provides a README in the goldens directory and a script
assist in testing the current state of the repo against the goldens as
well as a command for accepting all changes to the goldens in a single
command.

PR Close #35768
2020-03-10 20:58:39 -04:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
Revert "fix(router): state data missing in routerLink (#33203)" (#35882)
2020-03-05 17:43:03 -05:00
test
test(router): use pageYOffset in testing when scrollY is not available (#35976)
2020-03-10 13:28:04 -04:00
testing
refactor(core): Migrate TestBed.get to TestBed.inject (#32382)
2019-09-09 19:10:54 -04:00
upgrade
test: setup circular dependency tests for all entry points (#34774)
2020-01-23 11:36:40 -08:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
ci: move public-api goldens to goldens directory (#35768)
2020-03-10 20:58:39 -04: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
build: reference zone.js from source directly instead of npm. (#33046)
2019-11-06 00:48:34 +00:00
package.json
build(packaging): add repository.directory field to package.jsons (#27544)
2020-02-25 13:12:45 -08: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.