Skip to content
/ stepc Public
forked from creationix/step

A CoffeeScript-safe version of creationix' step

Notifications You must be signed in to change notification settings

akidee/stepc

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

23 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Step

A simple control-flow library for node.JS that makes parallel execution, serial execution, and error handling painless.

Installation

npm install stepc

How to use

The step library exports a single function I call Step. It accepts any number of functions as arguments and runs them in serial order using the passed in this context as the callback to the next step.

Step(
  function readSelf() {
    fs.readFile(__filename, this);
  },
  function capitalize(err, text) {
    if (err) throw err;
    return text.toUpperCase();
  },
  function showIt(err, newText) {
    if (err) throw err;
    console.log(newText);
  }
);

Notice that we pass in this as the callback to fs.readFile. When the file read completes, step will send the result as the arguments to the next function in the chain. Then in the capitalize function we're doing synchronous work so we can simple return the new value and Step will route it as if we called the callback.

The first parameter is reserved for errors since this is the node standard. Also any exceptions thrown are caught and passed as the first argument to the next function. As long as you don't nest callback functions inline your main functions this prevents there from ever being any uncaught exceptions. This is very important for long running node.JS servers since a single uncaught exception can bring the whole server down.

Also there is support for parallel actions:

Step(
  // Loads two files in parallel
  function loadStuff() {
    fs.readFile(__filename, this.parallel());
    fs.readFile("/etc/passwd", this.parallel());
  },
  // Show the result when done
  function showStuff(err, code, users) {
    if (err) throw err;
    sys.puts(code);
    sys.puts(users);
  }
)

Here we pass this.parallel() instead of this as the callback. It internally keeps track of the number of callbacks issued and preserves their order then giving the result to the next step after all have finished. If there is an error in any of the parallel actions, it will be passed as the first argument to the next step.

Also you can use group with a dynamic number of common tasks.

Step(
  function readDir() {
    fs.readdir(__dirname, this);
  },
  function readFiles(err, results) {
    if (err) throw err;
    // Create a new group
    var group = this.group();
    results.forEach(function (filename) {
      if (/\.js$/.test(filename)) {
        fs.readFile(__dirname + "/" + filename, 'utf8', group());
      }
    });
  },
  function showAll(err , files) {
    if (err) throw err;
    sys.p(files);
  }
);

Note that we both call this.group() and group(). The first reserves a slot in the parameters of the next step, then calling group() generates the individual callbacks and increments the internal counter.

Ignore returned values

It can be useful to ignore the functions' returned values, especially in JavaScript compiled from CoffeeScript, where the result of the last expression is always returned and will trigger the next step while ignoring callbacks. The way to be sure that all steps are asynchronous is:

Step.async(
  function () {

    // This is what the CoffeeScript compiler does
    return fs.readdir(__dirname, this);
  },
  function (err, results) {
    // ...
  }
)

Preserve context

To preserve the current context is to pass it to Step() as the first argument. this will be the context you provide, your callback is now an additional argument that is passed to every function:

Step(
  this,
  function(e, next) {
    // You can continue to use `this` here, how you would expect it.
    doAsync(..., next);
  },
  function(e, result, next) {
    doAsync(..., next.parallel());
    doAsync(..., next.parallel());
  },
  function(e, result1, result2) {
    // ...
  }
)

next can never be the first argument, since, by convention, it points to an error.

About

A CoffeeScript-safe version of creationix' step

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 100.0%