chainit

Turn an asynchronous JavaScript api into an asynchronous chainable JavaScript api.

chainit3

Turn an asynchronous JavaScript api into an asynchronous chainable JavaScript api.

This is a fork of chainit, with more work into getting a well-defined behavior of the transformation.

function MyApi() {}
MyApi.prototype.method1 = function(cb) {cb()}
MyApi.prototype.method2 = function(cb) {cb()}
 
var chainit = require('chainit');
var MyChainApi = chainit(MyApi);
var obj = new MyChainApi();
obj
  .method1()                      // 1st call 
  .method2()                      // 2nd call 
  .method1(function(/* args */) { // 3rd call 
    this.method1();               // 4th call 
  })
  .method2();                     // 5th call 

Adding and overriding methods works at both prototype level and instance level.

You must use chainit.add(chain, methodName, method), since direct assignations won't wrap your method properly.

function MyApi() {}
MyApi.prototype.method1 = function(cb) {cb()}
MyApi.prototype.method2 = function(cb) {cb()}
 
var chainit = require('chainit');
var MyChainApi = chainit(MyApi);
 
var obj = new MyChainApi();
 
// override instance method 
chainit.add(obj, 'method1', function(cb) {
  cb()
});
 
obj
  .method1() // calls the newly added method1 
  .method2();
 
// revert original method 
chainit.add(obj, 'method1', MyApi.prototype.method1);
 
// override prototype method 
chainit.add(MyChainApi, 'method1', function(cb) {
  cb()
});
 
var obj2 = new MyChainApi();
 
obj2.method1(); // calls the newly chained prototype `method1` 

It is also possible to have a custom function called immediately, in addition to the function that is queued:

chainit.add(obj, 'method1', function queued1(subcb) {
  //... the actual method 
}, function now1(sub) {
  this.chainState = { one: true };
});
chainit.add(obj, 'method2', function queued2(var1var2cb) {
 
}, function now2(var1var2) {
  if (!this.chainState || !this.chainState.one) throw new Error("method2 must be called after method1");
  this.chainState.one = false;
});
 
// this works 
obj.method1(a, b).method2(a, b) // ok 
obj.method1(a, b, function() {
  this.method2(a, b); // ok 
  this.method2(a, b); // not allowed by that simple state machine 
});
 

The first function is pushed to the queue, the second function is called immediately.

The second function can set this.chainState = someObject and the queued function will be able to access that object.

this.chainState reference is copied to the next queued (and immediate if any) functions: this behavior allows queued functions to get information about which functions were queued before or after them.

Upon error, execution is stopped and the nearest callback is called, or the error is thrown:

obj
  .method1()
  .methodError()
  .notactuallycalled(function(err) {
    // the error that happened in methodError 
    // but the method "notactuallycalled" is not called ! 
    console.error(err);
  });

Uncaught errors are also caught and handled the same way - which adds some safety to the original API.

Methods that have a variable number of arguments require special handling. It is advised to define those methods with the smallest number of required arguments:

function(uricb) {
  var opts = {};
  if (typeof cb != "function") {
    opts = cb;
    cb = arguments[2];
  }
  // ... 
}

This automatically excludes the case where the function can accept (uri, myfun, cb) with myfun as an optional argument. This is actually a good thing because it prevents undefined behavior.

Features:

  • supports async apis
  • supports (crazy) nested calls
  • supports static and prototype methods
  • preserves nested calls order
  • preserves context in cb()
  • preserves cb(args)
  • stops execution on error
  • propagates error to the nearest callback
  • throws error if no callback can handle it
  • supports method(fun, cb) signatures
  • supports process.nextTick(cb)
  • supports setTimeout(cb)
  • supports methods redifinition
  • supports adding new methods
  • fully tested! local: npm install -g mocha && mocha, saucelabs: npm test

There is no easy way to mix sync/async chainable apis because there is no way to differenciate sync/async calls.

obj
  .asyncMethod()
  .syncMethod()

We cannot know that syncMethod is synchronous and that we do not need to wait for a callback to be called to continue.

Either your api is fully asynchronous and every method takes a callback.

Either your api is fully synchronous. If you want synchronous support, make a pull request adding chainit.sync(Constructor).

This module is using jessetane/queue.

A chainable api is queueing methods and reordering calls, so we use a queue.

This module was built to replace the chainable api from webdriverjs.

It is now used by more modules and is maintained with general use in mind now.