You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 31, 2022. It is now read-only.
To do the trick, however, the internal queue is always at 1 in this example:
var p = Handlebar.Promise();
p
.then(function(P) {
this.fulfill('foo'); //took me a second to realize this is the API and P is generally an object just for holding the value...
})
.then(function(P) {
console.log(P.value);
})
Unsure what I am missing, as the internal fulfill function is in use and working... just can't figure out how to expose it properly.
The text was updated successfully, but these errors were encountered:
Let me know if this was in-line with what you were thinking or is gonna have serious side-affects. You know this far far better than I, and have already implemented this "waiting" affect for LABjs
Which wouldn't be such a bad thing if I wasn't also looking for
deferred
to work (which I am going after next)...I would have expected:
To do the trick, however, the internal queue is always at 1 in this example:
var p = Handlebar.Promise();
p
.then(function(P) {
this.fulfill('foo'); //took me a second to realize
this
is the API and P is generally an object just for holding the value...})
.then(function(P) {
console.log(P.value);
})
Unsure what I am missing, as the internal fulfill function is in use and working... just can't figure out how to expose it properly.
The text was updated successfully, but these errors were encountered: