Added callback for Network.stop
Outmost brackets are no longer automatically converted to connect and disconnect events. Instead, connect and disconnect are injected as needed, but only for subscribers of the legacy events
Added deprecation warnings for APIs that will be removed by NoFlo 1.0. These can be made fatal by setting the NOFLO_FATAL_DEPRECATED environment variable. These include:
- noflo.AsyncComponent: should be ported to Process API
- noflo.helpers.MapComponent: should be ported to Process API
- noflo.ArrayPort: should be ported to noflo.In/OutPort with addressable: true
- noflo.Port: should be ported to noflo.In/OutPort
- Calling Network.start or Network.stop without a callback
- noflo.InPort process option: should be ported to Process API or use the handle option
- noflo.InPort receive method: replaced by the get method
- noflo.InPort contains method: replaced by the has method
- noflo.Graph exports: use specific inport or outport instead
- Additionally component.io builds warn about deprecation in favor of webpack with helpful automation available in grunt-noflo-browser
Added IP object scope support to WirePattern to make WirePattern components more concurrency-friendly
Removed receiveStreams option from WirePattern
Graph JSON schema has been moved to https://github.com/flowbased/fbp, and updated with tests.
Added stream helpers for Process API input. hasStream checks if an input buffer contains a complete stream (matching brackets and data, or only data), getStream returns a complete stream of packets. These require forwardBrackets to be disabled for the port.
babel-core was removed as a dependency. Install separately for projects needing ES6 component support
underscore.js was removed as a dependency
input.getData() in Process API has been changed to fetch only packets of data type skipping and dropping brackets inbetween
IP objects are strictly required to be of noflo.IP type
Removed support for deprecated Node.js 0.x versions
NoFlo Graph and Journal were moved to a dedicated fbp-graph library for easier usage in other FBP projects. No changes to NoFlo interface
NoFlo networks now emit packet events only while the network is running
NoFlo networks can show their currently active processes with the getActiveProcesses() method

0.7.9

Diff

bergie

published 0.7.9 • 8 years ago

0.7.8

Diff

bergie

published 0.7.8 • 8 years ago

Changelog

Source

0.7.8 (June 10th 2016)

Added input buffer manipulation methods
Added support for falsy IP object scopes
Added support for sending values out directly with output.send if there is only one non-error outport
InternalSocket no longer re-wraps already-wrapped errors coming from downstream
Switched NoFlo's default browser builder to webpack

0.7.7

Diff

bergie

published 0.7.7 • 8 years ago

Changelog

Source

0.7.7 (June 8th 2016)

input.has now accepts a validation callback function as the last argument. All packets in buffer will be passed to this function, and has will return false only if something returns true for each port specified
Removed dropEmptyBrackets option which was conflicting with asynchronous components. This results into empty brackets being forwarded to error outport, so make sure error handling components don't make false alerts on those.
ComponentLoader was refactored to allow easier injection of custom loaders when dealing with bundling tools like Browserify and Webpack

0.7.6

Diff

bergie

published 0.7.6 • 8 years ago

Changelog

Source

0.7.6 (June 2nd 2016)

Fixed ComponentLoader caching on Node.js
Added support for stream datatype in ports, allowing streams to be passed as data packets
NoFlo Graphs now support case sensitive mode, which is possible to trigger via options

0.7.5

Diff

bergie

published 0.7.5 • 9 years ago

Changelog

Source

0.7.5 (May 2nd 2016)

Added automatic bracket forwarding via forwardBrackets option. Enabled from in port to out and error ports by default.
Empty brackets are not forwarded to ports in dropEmptyBrackets list (defaults to ['error']).
IP metadata can easily be forwarded in simple components by using output.pass() instead of output.sendDone().

0.7.4

Diff

bergie

published 0.7.4 • 9 years ago

Changelog

Source

0.7.4 (April 7th 2016)

Minor network starting improvement

0.7.3

Diff

bergie

published 0.7.3 • 9 years ago

Changelog

Source

0.7.3 (April 7th 2016)

Fixed error handling on broken FBP manifest data
Fixed network start callback when there are no defaults in a graph
Network uptime is now calculated from the first start event, not from initialization