ec4381dd40
This commit switches the default value of the enableIvy flag to true. Applications that run ngc will now by default receive an Ivy build! This does not affect the way Bazel builds in the Angular repo work, since those are still switched based on the value of the --define=compile flag. Additionally, projects using @angular/bazel still use View Engine builds by default. Since most of the Angular repo tests are still written against View Engine (particularly because we still publish VE packages to NPM), this switch also requires lots of `enableIvy: false` flags in tsconfigs throughout the repo. Congrats to the team for reaching this milestone! PR Close #32219 |
||
|---|---|---|
| .. | ||
| app | ||
| README.md | ||
| e2e-spec.ts | ||
| example-config.json | ||
| index.html | ||
| karma-test-shim.js | ||
| karma.conf.js | ||
| run-unit-tests.sh | ||
| systemjs.config.1.js | ||
| tsconfig.json | ||
README.md
This is the Angular Phonecat application adjusted to fit our boilerplate project structure.
The following changes from vanilla Phonecat are applied:
- Karma config for unit tests is in karma.conf.ng1.js because the boilerplate Karma config is not compatible with the way tests in this project need to be run. The shell script run-unit-tests.sh can be used to run the unit tests.
- E2E tests have been moved to the parent directory, where
run-e2e-testscan discover and run them along with all the other examples. - Most of the phone JSON and image data removed in the interest of keeping repo weight down. Keeping enough to retain testability of the app.
Running the app
Start like any example
npm run start
Running E2E tests
Like for any example (at the project root):
gulp run-e2e-tests --filter=phonecat-3