RSVP.js
RSVP.js provides simple tools for organizing asynchronous code.
Specifically, it is a tiny implementation of Promises/A+ and a
mixin for turning objects into event targets.
It works in node and the browser.
downloads
Promises
Bower
bower install -S rsvp
NPM
npm install --save rsvp
RSVP.Promise
is an implementation of
Promises/A+ that passes the
test suite.
It delivers all promises asynchronously, even if the value is already
available, to help you write consistent code that doesn't change if the
underlying data provider changes from synchronous to asynchronous.
It is compatible with TaskJS, a library by Dave
Herman of Mozilla that uses ES6 generators to allow you to write
synchronous code with promises. It currently works in Firefox, and will
work in any browser that adds support for ES6 generators. See the
section below on TaskJS for more information.
Basic Usage
var promise = new RSVP.Promise(function(resolve, reject){
resolve(value);
reject(error);
});
promise.then(function(value) {
}, function(value) {
});
Once a promise has been resolved or rejected, it cannot be resolved or
rejected again.
Here is an example of a simple XHR2 wrapper written using RSVP.js:
var getJSON = function(url) {
var promise = new RSVP.Promise(function(resolve, reject){
var client = new XMLHttpRequest();
client.open("GET", url);
client.onreadystatechange = handler;
client.responseType = "json";
client.setRequestHeader("Accept", "application/json");
client.send();
function handler() {
if (this.readyState === this.DONE) {
if (this.status === 200) { resolve(this.response); }
else { reject(this); }
}
};
});
return promise;
};
getJSON("/posts.json").then(function(json) {
}, function(error) {
});
Chaining
One of the really awesome features of Promises/A+ promises are that they
can be chained together. In other words, the return value of the first
resolve handler will be passed to the second resolve handler.
If you return a regular value, it will be passed, as is, to the next
handler.
getJSON("/posts.json").then(function(json) {
return json.post;
}).then(function(post) {
});
The really awesome part comes when you return a promise from the first
handler:
getJSON("/post/1.json").then(function(post) {
return getJSON(post.commentURL);
}).then(function(comments) {
});
This allows you to flatten out nested callbacks, and is the main feature
of promises that prevents "rightward drift" in programs with a lot of
asynchronous code.
Errors also propagate:
getJSON("/posts.json").then(function(posts) {
}).then(null, function(error) {
});
You can use this to emulate try/catch
logic in synchronous code.
Simply chain as many resolve callbacks as a you want, and add a failure
handler at the end to catch errors.
getJSON("/post/1.json").then(function(post) {
return getJSON(post.commentURL);
}).then(function(comments) {
}).then(null, function(error) {
});
You can also use fail
for error handling, which is a shortcut for
then(null, rejection)
, like so:
getJSON("/post/1.json").then(function(post) {
return getJSON(post.commentURL);
}).fail(function(error) {
});
Error Handling
There are times when dealing with promises that it seems like any errors
are being 'swallowed', and not properly raised. This makes is extremely
difficult to track down where a given issue is coming from. Thankfully,
RSVP
has a solution for this problem built in.
You can register functions to be called when an uncaught error occurs
within your promises. These callback functions can be anything, but a common
practice is to call console.assert
to dump the error to the console.
RSVP.on('error', function(event) {
console.assert(false, event.detail);
});
NOTE: Usage of RSVP.configure('onerror', yourCustomFunction);
is
deprecated in favor of using RSVP.on
.
Arrays of promises
Sometimes you might want to work with many promises at once. If you
pass an array of promises to the all()
method it will return a new
promise that will be fulfilled when all of the promises in the array
have been fulfilled; or rejected immediately if any promise in the array
is rejected.
var postIds = [2, 3, 5, 7, 11, 13];
var promises = [];
for(var i = 0; i < postIds.length; i++) {
promises.push(getJSON("/post/" + postIds[i] + ".json"));
}
RSVP.all(promises).then(function(posts) {
});
Hash of promises
If you need to reference many promises at once (like all()
), but would like
to avoid encoding the actual promise order you can use hash()
. If you pass
an object literal (where the values are promises) to the hash()
method it will
return a new promise that will be fulfilled when all of the promises have been
fulfilled; or rejected immediately if any promise is rejected.
The key difference to the all()
function is that both the fulfillment value
and the argument to the hash()
function are object literals. This allows
you to simply reference the results directly off the returned object without
having to remember the initial order like you would with all()
.
var promises = {
posts: getJSON("/posts.json"),
users: getJSON("/users.json")
};
RSVP.hash(promises).then(function(results) {
console.log(results.users)
console.log(results.posts)
});
Deferred
RSVP also has a RSVP.defer() method that returns a deferred object of the form
{ promise, resolve(x), reject(r) }
. This creates a deferred object without
specifying how it will be resolved. However, the RSVP.Promise
constructor is
generally a better and less error-prone choice; we recommend using it in
preference to RSVP.defer()
.
TaskJS
The TaskJS library makes it possible to take
promises-oriented code and make it synchronous using ES6 generators.
Let's review an earlier example:
getJSON("/post/1.json").then(function(post) {
return getJSON(post.commentURL);
}).then(function(comments) {
}).then(null, function(error) {
});
Without any changes to the implementation of getJSON
, you could write
the following code with TaskJS:
spawn(function *() {
try {
var post = yield getJSON("/post/1.json");
var comments = yield getJSON(post.commentURL);
} catch(error) {
}
});
In the above example, function *
is new syntax in ES6 for
generators.
Inside a generator, yield
pauses the generator, returning control to
the function that invoked the generator. In this case, the invoker is a
special function that understands the semantics of Promises/A, and will
automatically resume the generator as soon as the promise is resolved.
The cool thing here is the same promises that work with current
JavaScript using .then
will work seamlessly with TaskJS once a browser
has implemented it!
Event Target
RSVP also provides a mixin that you can use to convert any object into
an event target. The promises implementation uses RSVP.EventTarget
, so
RSVP
exposes it for your own use.
Basic Usage
The basic usage of RSVP.EventTarget
is to mix it into an object, then
use on
and trigger
to register listeners and trigger them.
var object = {};
RSVP.EventTarget.mixin(object);
object.on("finished", function(event) {
});
object.trigger("finished", { detail: value });
Prototypes
You can mix RSVP.EventTarget
into a prototype and it will work as
expected.
var Person = function() {};
RSVP.EventTarget.mixin(Person.prototype);
var yehuda = new Person();
var tom = new Person();
yehuda.on("poke", function(event) {
console.log("Yehuda says OW");
});
tom.on("poke", function(event) {
console.log("Tom says OW");
});
yehuda.trigger("poke");
tom.trigger("poke");
The example will work as expected. If you mix RSVP.EventTarget
into a
constructor's prototype, each instance of that constructor will get its
own callbacks.
Instrumentation
function listener (event) {
event.guid
event.childGuid
event.eventName
event.detail
event.label
event.timeStamp
}
RSVP.configure('instrument', true | false);
RSVP.on('created', listener);
RSVP.on('chained', listener);
RSVP.on('fulfilled', listener);
RSVP.on('rejected', listener);
Events are only triggered when RSVP.configure('instrument')
is true, although
listeners can be registered at any time.
Building & Testing
This package uses the grunt-microlib package for building.
Custom tasks:
grunt test
- Run Mocha tests through Node and PhantomJS.grunt test:phantom
- Run Mocha tests through PhantomJS (browser build).grunt test:node
- Run Mocha tests through Node (CommonJS build).grunt docs
- Run YUIDoc, outputting API documentation to docs
folder.