Hi Sander,
great to hear. Thanks for information.
Regards
Am Montag, 9. März 2015 15:40:31 UTC+1 schrieb Sander Elias:
>
> Hi Martin,
>
> As far as I found out, on the moment, yes, you have to do it on your own.
> However, this is going to change as soon as the new formCollection thingie
> will
Hi Martin,
As far as I found out, on the moment, yes, you have to do it on your own.
However, this is going to change as soon as the new formCollection thingie
will materialize. Also during the ng-conf I heard Misko talking about that
for the developer there would not be a big difference between
What I mean is: do we really have to do the update to the model manually.
As in the example, which means listen on a change or key... event and to
call a method which updates the model (no other way to get the value back
to the model)
I suppose this is the case, but of course this is much less
I am messing around with this right now too :-)
Try
value={{name}}
Just found out camelCase for variable names is a bad idea
#newName did not make it to my function. (maybe gets converted to new-name)
On 9 March 2015 at 15:44, Martin Kuhn wrote:
> I'm curious about two way databinding in An
I'm curious about two way databinding in Angular2.
I played around with the quickstart project and would like to know how to
get a value from an UI-element back to the model:
In the source example I used the change event and a manually update of the
model.
But this may not be the right way, o