The docs aren't clear about this, but this has been a feature since CanJS 1.x that if your view data is a deferred, you will get a deferred back. Example from my Chrome console:
$("<script type='text/mustache' id='fooscript'><span>foo! {{text}}</span></script>").appendTo(document.body)
[
- <script type="text/mustache" id="fooscript"><span>foo! {{text}}</span></script>
can.view("fooscript", new $.Deferred().resolve({ text : "bar"}))
Object {resolve: function, resolveWith: function, reject: function, rejectWith: function, notify: function…}
can.view("fooscript", { text : "bar"})
- #document-fragment
this is not the case when your view is in the form of a function, though:
stache = can.view.mustache("<span>foo! {{text}}</span>")
function () {
return $view.frag(renderer.render.apply(this, arguments));
}
can.view(stache, { text : "Bar" })
- #document-fragment
can.view(stache, $.when({text : "Bar" }))
- #document-fragment
