Calling ko.mapping.fromJS() inside a ko.computed cause endless loop about knockout.mapping HOT 9 CLOSED

I think it shouldn't be an computed observable, but a normal anonymous function.

from knockout.mapping.

No I need it to be computed, because I want the ajax loading be run each time I changed the current client

from knockout.mapping.

Then you need to subscribe on the current client. http://knockoutjs.com/documentation/observables.html#explicitly_subscribing_to_observables
Because the $.ajax method is asynchronous.

from knockout.mapping.

Yes, inside the function I have var client = data.curClient();, that statement makes the computed function get called everytime the curClient changes

from knockout.mapping.

No, you should subscribe, as mentioned on the page i linked for you, on the data.curClient like this:

data.curClient.subscribe(function(newValue) {
    // this function will every time executed when data.curClient changes.
    // put here your ajax request, like the code you had in your first message in the ko.computed block.

});

from knockout.mapping.

I read that. What's difference between it and invoking the observable in a ko.computed ? I was always using ko.computed without any problem until I met this issue

from knockout.mapping.

We are actually talking about the way how to implement. But maybe it's a good idea to create a fiddle? So we can dig into your actually problem (an infinite loop) a bit better.

from knockout.mapping.

No reply for over a month. Please feel free to reopen this issue!

from knockout.mapping.

hi greenlaw110

Did you find the reason why this issues was happening and what you did to solve the issue? Can you please share?

Regards

from knockout.mapping.