Can deferred updates handle the following scenario? If not, I'm considering forking.
myObservable(newValue);
Imagine a paged list of items with a search filter. When you switch pages you switch pages, your updating the pageNumber observable. When the filter updates, you're updating the filter observable, but also calling:
pageNumber(1);
Then there's a third computed observable (called query) that returns the wrapped values of both the filter and current page to a client that will make an ajax call. The client has subscribed to query, but when you update the filter, query updates twice (once because filter has changed and once because pageNumber has been changed by the filter subscribe).
Can deferred updates handle the following scenario? If not, I'm considering forking.
myObservable(newValue);
Imagine a paged list of items with a search filter. When you switch pages you switch pages, your updating the pageNumber observable. When the filter updates, you're updating the filter observable, but also calling:
pageNumber(1);
Then there's a third computed observable (called query) that returns the wrapped values of both the filter and current page to a client that will make an ajax call. The client has subscribed to query, but when you update the filter, query updates twice (once because filter has changed and once because pageNumber has been changed by the filter subscribe).
Here's a jsfiddle for the scenario: http://jsfiddle.net/edUxS/9/
Thanks.