as a reader I would like to know about the 'Change' trickery in two way bindings about ngcourse2 HOT 2 CLOSED

I was playing around with a plunker on this a few days ago, link

Basically, if your component has input/output naming convention like

export default class SomeComponent {
@Input() someThing: string;
@Output() someThingChange = new EventEmitter();
}

You can setup two way binding with

<some-component [(someThing)]="myValue"></some-component>

If you want to do something else in addition to syncing up myValue, you can mix/match.

<some-component [(someThing)]="myValue" (someThingChange)="doExtraStuff($event)"></some-component>

So if you want to keep the value in sync, but maybe do some other stuff as a result - can still do both.

Fleshing out the two-way binding card to include a bit of this would be good.

from ngcourse2.

That looks good. Varun also has an example that shows this off in the "pizza form".

from ngcourse2.