honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
ggradnig 71f008f906 fix(router): remove parenthesis for primary outlet segment after removing auxiliary outlet segment (#24656) (#37163) 
For URLs that use auxiliary route outlets in the second or following path segments,
when removing the auxiliary route segment, parenthesis remain for the primary outlet segment.
This causes the following error when trying to reload an URL: "Cannot match any route".
The commit adds a check for this scenario, serializing the URL as "a/b" instead of "a/(b)".

PR Close #24656

PR Close #37163
2020-06-18 16:02:19 -07:00
..
scripts
…
src
fix(router): remove parenthesis for primary outlet segment after removing auxiliary outlet segment (#24656) (#37163)
2020-06-18 16:02:19 -07:00
test
fix(router): remove parenthesis for primary outlet segment after removing auxiliary outlet segment (#24656) (#37163)
2020-06-18 16:02:19 -07:00
testing
docs(router): fix a typo in example code (#37309)
2020-06-01 17:19:45 -04:00
upgrade
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
.gitignore
…
BUILD.bazel
build: provide full paths to ts_api_guardian_test_npm_package and ts_api_guardian_test (#36034)
2020-03-12 09:49:00 -07:00
index.ts
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
karma-test-shim.js
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04:00
karma.conf.js
feat(zone.js): upgrade zone.js to angular package format(APF) (#36540)
2020-06-11 11:08:48 -07:00
package.json
Revert "build: remove wombot proxy registry from package.jsons for release (#37378)" (#37495)
2020-06-10 08:21:45 -07:00
PACKAGE.md
docs: add package doc files (#26047)
2018-10-05 15:42:14 -07:00
public_api.ts
build: update license headers to reference Google LLC (#37205)
2020-05-26 14:26:58 -04: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.