cyclejs/cyclejs v0.18.0

v0.18.0 - Small breaking change on DataFlowSink, plus improvements

on GitHub

The only breaking change in this version is very small: DataFlowSink.inject() now returns the input it was given, instead of returning the Rx.Disposable that the definitionFn of DataFlowSink returns. This makes DataFlowSink consistent with DataFlowNode and DataFlowSource.

BEFORE

sink.inject(node1).inject(node2); // THROWS ERROR because sink.inject(node1) returns Rx.Disposable

AFTER

sink.inject(node1).inject(node2); // works fine, because sink.inject(node1) returns node1

dispose() function on DataFlowNode and DataFlowSink. These classes contain Rx.Disposable internally, and in the rare use case that you need to dispose them, this function allows you to do that. Normally you don't need to do this since DataFlowNodes are created once on application bootstrap and intended to live forever during the application run. Use dispose() in case you are dynamically creating and destroying DataFlowNodes.

get() function added to DataFlowSource. It was missing and should exist to stay consistent with DataFlowNode.

These are the functions that each type contains.

| contains? | DataFlowSource | DataFlowNode | DataFlowSink |
|-----------|----------------|--------------|--------------|
| get()     | YES            | YES          | no           |
| inject()  | no             | YES          | YES          |
| dispose() | no             | YES          | YES          |