You can’t call something on the entire viewModel, but on an individual observable you can call myObservable.valueHasMutated() to notify subscribers that they should re-evaluate. This is generally not necessary in KO, as you mentioned.
Have you tried calling knockout’s clean node method on your DOM element to dispose of the in memory bound objects? var element = $(‘#elementId’)[0]; ko.cleanNode(element); Then applying the knockout bindings again on just that element with your new view models would update your view binding.
Check this http://jsfiddle.net/pTEbA/268/ Object.prototype.getName = function() { var funcNameRegex = /function (.{1,})\(/; var results = (funcNameRegex).exec((this).constructor.toString()); return (results && results.length > 1) ? results[1] : “”; }; function StateViewModel(data){ this.name = ko.observable(); ko.mapping.fromJS(data, mapping, this); } function CityViewModel(data) { this.name = ko.observable(); ko.mapping.fromJS(data, mapping, this); } function StreetViewModel(data) { this.name = ko.observable(); ko.mapping.fromJS(data, mapping, this); … Read more
I think I have summarized all your questions, if I missed something please let me know (If you could summarize up all your questions in one place would be nice =)) Note. Compatibility with the ko.editable plug-in added Download the full code How do you use html helpers with knockout.js This is easy: @Html.TextBoxFor(model => … Read more
Setting value of Knockout Observable / Observable Array doesn’t update You need to use the setter function to update the value of your observable / observableArray – Ex. 1 (observable) – var name=”John”; var myValue = ko.observable(); myValue(name); // Set myValue equal to John, update any subscribers var newObservable = ko.observable(‘Bill’); myValue(newObservable()); // Set myValue … Read more
This is related to the fact that browsers insert tbody tags automatically, which creates a mismatch in the comments. The rendered output will look like: <table> <!– ko foreach: MyPlans –> <tbody> <tr> <td>Test</td> </tr> <!– /ko –> </tbody> </table> Steve did put some work into trying to correct mismatched tags in KO, but the … Read more
If you add this element on the fly after you have bound your viewmodel it will not be in the viewmodel and won’t update. You can do one of two things. Add the element to the DOM and re-bind it by calling ko.applyBindings(); again OR add the list to the DOM from the beginning and … Read more
Normally this is not possible or advisable, as it potentially allows things to get out of sync in the dependency chains. Using the throttle extender is generally a good way to limit the amount of notifications that dependencies are receiving. However, if you really want to do this, then one option would be to overwrite … Read more
You could write a custom binding that sets the date in the field using the datepicker APIs and also sets the value of your observable by reading the date properly. The custom binding might look like: ko.bindingHandlers.datepicker = { init: function(element, valueAccessor, allBindingsAccessor) { var options = allBindingsAccessor().datepickerOptions || {}, $el = $(element); //initialize datepicker … Read more
There are a few directions that you could go with this one. One option is to call ko.applyBindings with distinct view models against separate DOM elements like: var viewModelA = { name: “Bob” }; var viewModelB = { price: 50 }; ko.applyBindings(viewModelA, document.getElementById(“aContainer”)); ko.applyBindings(viewModelB, document.getElementById(“bContainer”)); http://jsfiddle.net/9abgxn8k/ In this case, you would want to make sure … Read more