taskgroup
Advanced tools
Changelog
v4.0.3 2014 July 11
setImmediate
instead of nextTick
to avoid (node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.
errorsChangelog
v4.0.2 2014 June 18
done
, whenDone
, onceDone
, once
, and on
configuration optionsChangelog
v4.0.1 2014 June 16
Recursive process.nextTick detected
error (regression since v4.0.0)Changelog
v4.0.0 2014 June 16
.done(listener)
(listens once) or .whenDone(listener)
(listener persists)
done
eventsrc/lib/test/taskgroup-usage-test.coffee
for the guaranteed expectations across different scenariostasks.exit()
during execution to clear remaning items, stop execution, and exit, you can no longer do this, instead use the completion callback with an error, or call tasks.clear()
then the completion callbackcomplete
event is now completed
, but you really should be using the new done
event or the promise methodsrun
event is now started
error
and completed
listener that will emit the done
event if there are listeners for it, if there is no done
event listeners, and an error has occured, we will throw the error.createTask(...)
and .createGroup(...)
instead, then add the result manuallypassed
, failed
, destroyed
events are newtimeout
option that accepts a number of milliseconds to wait before throwing an erroronError
option that defaults to 'exit'
but can also accept 'ignore'
which will ignore duplicated exit errors (useful when combined with timeout event)onError
option that defaults to 'exit'
but can also accept 'ignore'
which will ignore all task errorssetNestedConfig(config)
and setNestedTaskConfig(config)
options to set configuration for all childrenChangelog
v3.3.9 2014 May 4
Task.create
and TaskGroup.create
helpersChangelog
v3.3.8 2014 February 5
Changelog
v3.3.7 2014 January 30