There are a couple of ways that you can handle a situation like this one. You can either choose to address it through bindings or push it into your view model.
If your view model is created by the mapping plugin and you don't want to get into customizing the way that it is created, then you can consider using a custom binding that is a wrapper to the text binding to handle the formatting.
Something like (http://jsfiddle.net/rniemeyer/RVL6q/):
ko.bindingHandlers.numericText = {
update: function(element, valueAccessor, allBindingsAccessor) {
var value = ko.utils.unwrapObservable(valueAccessor()),
precision = ko.utils.unwrapObservable(allBindingsAccessor().precision) || ko.bindingHandlers.numericText.defaultPrecision,
formattedValue = value.toFixed(precision);
ko.bindingHandlers.text.update(element, function() { return formattedValue; });
},
defaultPrecision: 1
};
It certainly would be possible to create an even more generic binding (formattedText) that either inspected the value and formatted it using some overridable defaults or allowed you to pass in some formatting options ({ type: "numeric", precision: 2 }
).
For your scenario, it sounds like the first option might be a good choice. However, if you want to push it into your view model, then you could create a special observable that can return both a formatted and a raw version of the value.
It could be something like (http://jsfiddle.net/rniemeyer/fetBG/):
function formattedNumericObservable(initialValue, precision) {
var _raw = ko.observable(initialValue),
precision = precision || formattedNumericObservable.defaultPrecision,
//the dependentObservable that we will return
result = ko.dependentObservable({
read: function() {
return _raw().toFixed(precision);
},
write: _raw
});
//expose raw value for binding
result.raw = _raw;
return result;
}
Now you could potentially bind against myValue
and myValue.raw
depending on your needs. Otherwise, you could flip it and return the raw value by default and expose a formatted
dependentObservable. When an object like this is converted to JSON, it will lose any of the "sub-observables", so if you are sending this data back to a server that might be a consideration.
You could again make it more generic and create a formattedObservable
that takes in some information about how to format the object.
Finally, 1.3 beta offers an extenders
API. You could do something similar to above like: (http://jsfiddle.net/rniemeyer/AsdES/)
ko.extenders.numeric = function(target, precision) {
var result = ko.dependentObservable({
read: function() {
return target().toFixed(precision);
},
write: target
});
result.raw = target;
return result;
};
Then, apply it to an observable like: var myValue = ko.observable(1.223123).extend({numeric: 1});
You could have the extender also just add a formatted
dependentObservable to target
instead of returning the dependentObservable itself.