eventuate-chainable

Create eventuates that consume from other eventuates.

example

var eventuate          = require('eventuate-core'),
    eventuateChainable = require('eventuate-chainable')
 
// create a chainable eventuate mapper
var map = eventuateChainable(function eventuateMap (options, map) {
  return function forEachValue (value) {
    this.produce(map(value))
    this.finish()
  }
})
 
// create an eventuate
var numbers = eventuate()
 
// map the eventuate using the chainable mapper we created above
var squareNumbers = map(numbers, function (num) {
  return num * num
})
 
// log anything produced by squareNumbers
squareNumbers(console.log)
 
// produce stuff on numbers, the square of it is logged via squareNumbers
numbers.produce(1)
numbers.produce(2)
numbers.produce(3)
numbers.produce(4)

api

var chainable = require('eventuate-chainable')

chainableFactory = chainable([defaults], producerFactory)

Create a chainable eventuate factory, chainableFactory, that can be used to create new eventuates that consume from other eventuates. Accepts an optional defaults, which will set the default set of options for chainable eventuates created by the factory, and producerFactory, which will be invoked when the chainableFactory is called to create an eventuate, and is expected to return a function that accepts data produced by an upstream eventuate.

The factory returned has a signature of:

function chainableFactory (upstreamEventuate [, options, arg3, arg4, ...]) {}

The only required argument for the chainableFactory us the upstreamConsumer from which it will consume. If options are provided, they will be merged with defaults set at the time the chainableFactory was created.

When chainableFactory is called, it will call producerFactory, which is expected to have a signature of:

function producerFactory (options [, arg3, arg4, ...]) {}

The producerFactory will be called with options (which has been merged with defaults), and any other arguments that were supplied to chainableFactory after options.

producerFactory is expected to return a function that will be called for each thing produced by upstreamEventuate. This function should have the signature of:

function producer (data) {}

This producer function is called in the context of an object that offers the following:

• produce(data) - call this to produce data from the eventuate created by chainableFactory. Returns reference to context object. If the eventuate was destroyed prior to calling this, the data will be dropped.
• error(err) - call this to produce an error from the eventuate created by chainableFactory. This function will insure whatever is passed is wrapped in an Error object if it's not already an instanceof Error. Returns a reference to the context object. If the eventuate was destroyed prior to calling this, the data will be dropped.
• finish() - call this to signal no more data or errors will be produced. It is important to call this, or all future produce calls could be buffered.

behaviour

Chainable eventuates produced in this way have the following (default) characteristics:

unordered

Chainable eventuates, by default, do not gaurantee that the order they consume data is the order they will produce it. This can be changed by setting the option { order: true }. Be warned, that this will cause buffering, and should be used with caution.

lazy consumption

Chainable eventuates do not start consuming from their upstream eventuate until a consumer has been added. This can be changed by setting the option { lazy: false }.

infinite concurrency

Async producers have no limits on concurrency by default. You can change this by setting the option { concurrency: X } where X is the max level of concurrency. Be warned, this will cause buffering when maximum concurrency is reached. Pending events will be buffered and started as able.

upstream consumer maintained

If the upstreamConsumer added to the upstreamEventuate by the chainable eventuate is removed for any reason (such as removeAllConsumers being called on the upstreamEventuate), it will be replaced immediately. If either the upstreamEventuate or the chainable eventuate are destroyed, the upstreamConsumer will be removed as expected.

residuals destroyed

By default, when the last consumer is removed from a chainable eventuate, the chainable eventuate is destroyed (destroy() is called). This can be changed by setting the option { destroyResidual: false }.

install

With npm do:

npm install --save eventuate-chainable

testing

npm test

Or to run tests in phantom: npm run phantom

coverage

npm run view-cover

This will output a textual coverage report.

npm run open-cover

This will open an HTML coverage report in the default browser.