angular-cn/aio/content/examples/upgrade-phonecat-3-final
Alex Rickabaugh ec4381dd40 feat: make the Ivy compiler the default for ngc (#32219)
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
2019-08-20 16:41:08 -07:00
..
app docs: migrate examples from @angular/http to @angular/common/http (#28296) 2019-03-11 10:52:17 -07:00
README.md docs(aio): rework of the upgrade guide 2017-05-19 09:42:17 +01:00
e2e-spec.ts docs(aio): rework of the upgrade guide 2017-05-19 09:42:17 +01:00
example-config.json build(aio): change examples to CLI (#19248) 2017-09-21 17:05:54 -07:00
index.html docs(aio): rework of the upgrade guide 2017-05-19 09:42:17 +01:00
karma-test-shim.js docs: migrate examples from @angular/http to @angular/common/http (#28296) 2019-03-11 10:52:17 -07:00
karma.conf.js fixup! docs: update Universal guide (#28296) 2019-03-11 10:52:18 -07:00
run-unit-tests.sh docs(aio): replace “Angular 1” in upgrade phonecat script 2017-06-22 14:57:02 -07:00
systemjs.config.1.js docs: migrate examples from @angular/http to @angular/common/http (#28296) 2019-03-11 10:52:17 -07:00
tsconfig.json feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00

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-tests can 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