Call a function in ng:model

[tradeshift...@gmail.com]

hey Angulars,

can I call a function in ng:model instead of passing a string?

here is my code it seems I'm missing something!

http://jsfiddle.net/nicco/x5NYS/1/

Thanks and have a great day!

Nicco

[Ricardo Bin]

Hey Nicco,

Sorry, but i didnt understand your point. Whats your fiddle suppose to work?

[vinay...@gmail.com]

Yeah, you can use a function. In which case the ng-model will be the value returned by the function. 

If the returned value is an expression you will have to eval it yourself, I have changed your fiddle:

Doing an eval in markup:

http://jsfiddle.net/Amnesiac/x5NYS/3/ 

Doing an eval in the Ctrl:

http://jsfiddle.net/Amnesiac/x5NYS/5/ 

Vinay.

[nic...@gmail.com]

Thanks for the quick reply :)

[nic...@gmail.com]

Thats not a good news! So if setters don't work what can I do? Some workaround?

[Pawel Kozlowski]

hi!

On Mon, Aug 20, 2012 at 11:54 PM, <nic...@gmail.com> wrote:
> Thats not a good news! So if setters don't work what can I do? Some workaround?

Yeh, setters are not supported at the moment, there are couple of
issues already opened for this:

https://github.com/angular/angular.js/issues/768
https://github.com/angular/angular.js/issues/945

The only work-around I can think of is binding to a variable, watching
it (scope.$watch()) and invoking a setter in a watcher... didn't try
it in practice thought...

Cheers,
Pawel

[tradeshift...@gmail.com]

could it be a solution to create a directive that for every generic element does get the path using the function and insert it in the ng:model? if yes will I have to create a directive for every kind of input or can I make a generic one? if yes can you explain how?

Thanks

Niccolo

[tradeshift...@gmail.com]

Looks like calling function in ng:model is not allowed at all in 1.0.1 :( not even for getters.