angular-cn/modules/playground
Paul Gschwendtner 5a257d02a6 build: fix "person_management" playground example (#28490)
Currently when someone serves the "person_management" playground
example, there will be runtime exceptions by `@angular/forms` if
someone clicks on one of the two buttons rendered in the example.

This happens because the example is outdated and the input elements
using `ngModel` do not specify a proper "name" while being inside of
a `<form>` element. A name is required inside of a form. The failure
is not specific to Ivy and is not covered by any test because the e2e
tests for this example are just asserting that the page properly loads
(the error only shows up one of the buttons has been clicked)

This is the reason why these errors were never visibile to the e2e tests.
Though in order to make this example work, we should this fix these failures
so that the example can work as expected.

```
FullNameComponent.html:7 ERROR Error: If ngModel is used within a form tag, either the name attribute must be set or the form
      control must be defined as 'standalone' in ngModelOptions.

      Example 1: <input [(ngModel)]="person.firstName" name="first">
      Example 2: <input [(ngModel)]="person.firstName" [ngModelOptions]="{standalone: true}">
    at Function.TemplateDrivenErrors.missingNameException (template_driven_errors.ts:40)
    at NgModel._checkName (ng_model.ts:319)
    at NgModel._checkForErrors (ng_model.ts:302)
    at NgModel.ngOnChanges (ng_model.ts:215)
    at Object.checkAndUpdateDirectiveInline (provider.ts:208)
    at checkAndUpdateNodeInline (view.ts:429)
    at checkAndUpdateNode (view.ts:389)
    at debugCheckAndUpdateNode (services.ts:431)
    at debugCheckDirectivesFn (services.ts:392)
    at Object.eval [as updateDirectives] (FullNameComponent.html:7)
```

PR Close #28490
2019-02-04 16:51:11 -05:00
..
e2e_test build: fix bazel protractor tests not capturing console output (#28490) 2019-02-04 16:51:11 -05:00
src build: fix "person_management" playground example (#28490) 2019-02-04 16:51:11 -05:00
BUILD.bazel build: switch playground examples to bazel (#28490) 2019-02-04 16:51:11 -05:00
README.md build: switch playground examples to bazel (#28490) 2019-02-04 16:51:11 -05:00
favicon.ico build: adding basic e2e testing infrastructure 2016-05-02 08:15:10 -07:00
systemjs-config.js build: switch playground examples to bazel (#28490) 2019-02-04 16:51:11 -05:00
systemjs-rxjs-operators.js build: switch playground examples to bazel (#28490) 2019-02-04 16:51:11 -05:00
tsconfig-build.json build: switch playground examples to bazel (#28490) 2019-02-04 16:51:11 -05:00

README.md

How to serve the examples

All playground examples are built and served with Bazel. Below is an example that demonstrates how a specific example can be built and served with Bazel:

# e.g. src/zippy_component
yarn bazel run modules/playground/src/zippy_component:devserver

# e.g. src/upgrade
yarn bazel run modules/playground/src/upgrade:devserver