51e716b6f2
Previously when testing code injected the Compiler, it received the top-level Compiler implementation defined in linker/compiler.ts (and governed by the __PRE_R3__ switch). Code running under the TestBed, however, should always use a TestBed-aware Compiler implementation. This commit adds such an implementation to the TestBedRender3, which passes compiled modules through the _compileNgModule() function. With this change, 3 formerly disabled router integration tests now pass. FW-855 #resolve PR Close #28033 |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| test | ||
| testing | ||
| upgrade | ||
| .gitignore | ||
| BUILD.bazel | ||
| PACKAGE.md | ||
| README.md | ||
| index.ts | ||
| karma-test-shim.js | ||
| karma.conf.js | ||
| 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 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.