93837e9545
Currently, calling `downgradeModule()` more than once is not supported. If one wants to downgrade multiple Angular modules, they can create a "super-module" that imports all the rest and downgrade that. This commit adds support for downgrading multiple Angular modules. If multiple modules are downgraded, then one must explicitly specify the downgraded module that each downgraded component or injectable belongs to, when calling `downgradeComponent()` and `downgradeInjectable()` respectively. No modification is needed (i.e. there is no need to specify a module for downgraded components and injectables), if an app is not using `downgradeModule()` or if there is only one downgraded Angular module. Fixes #26062 PR Close #26217 |
||
|---|---|---|
| .. | ||
| _common | ||
| common | ||
| compiler/ts/url_resolver | ||
| core | ||
| forms/ts | ||
| http/ts | ||
| platform-browser/dom/debug/ts | ||
| testing/ts | ||
| upgrade/static/ts | ||
| web_workers/ts | ||
| README.md | ||
| build.sh | ||
| test.sh | ||
| tsconfig-build.json | ||
| tsconfig.json | ||
README.md
API Examples
This folder contains small example apps that get in-lined into our API docs. Each example contains tests for application behavior (as opposed to testing Angular's behavior) just like an Angular application developer would write.
Running the examples
# # execute the following command only when framework code changes
./build.sh
# run when test change
./packages/examples/build.sh
# start server
$(npm bin)/gulp serve-examples
navigate to http://localhost:8001
Running the tests
# run only when framework code changes
./build.sh
# run to compile tests and run them
./packages/examples/test.sh
NOTE: sometimes the http server does not exit properly and it retains the 8001 port.
in such a case you can use lsof -i:8001 to see which process it is and then use kill
to remove it. (Or in single command: lsof -i:8001 -t | xargs kill)