@bergie bergie released this Nov 24, 2017 · 56 commits to master since this release

Added support for running arbitrary NoFlo graphs via noflo.asCallback. You can call this function now with either a component name, or a noflo.Graph instance


@bergie bergie released this Nov 3, 2017 · 106 commits to master since this release

  • The shipping NoFlo build is now using ES6 syntax, as provided by the CoffeeScript 2.x compiler. If you need to support older browsers or Node.js versions, you can transpile the code to ES5 using Babel
  • The APIs deprecated in NoFlo 0.8 were removed:
    • noflo.AsyncComponent class -- use WirePattern or Process API instead
    • noflo.ArrayPort class -- use InPort/OutPort with addressable: true instead
    • noflo.Port class -- use InPort/OutPort instead
    • noflo.helpers.MapComponent function -- use WirePattern or Process API instead
    • noflo.helpers.WirePattern legacy mode -- now WirePattern always uses Process API internally
    • noflo.helpers.WirePattern synchronous mode -- use async: true and callback
    • noflo.helpers.MultiError function -- send errors via callback or error port
    • noflo.InPort process callback -- use Process API
    • noflo.InPort handle callback -- use Process API
    • noflo.InPort receive method -- use Process API getX methods
    • noflo.InPort contains method -- use Process API hasX methods
    • Subgraph EXPORTS mechanism -- disambiguate with INPORT/OUTPORT
  • Improved errors thrown when trying to read from non-existing ports
  • Added unscoped support for outports. Setting scoped: false on an outport will force all packets sent to that port to be unscoped
  • Added a deprecation warning when loading legacy API components
  • More information on preparing for NoFlo 1.0 can be found from this blog post


@bergie bergie released this Sep 17, 2017 · 217 commits to master since this release

  • It is now possible to set individual ports to unscoped mode by setting the scoped: false parameter. This is useful for components that mix unscoped and scoped inputs
  • Ports and IP objects can now be annotated with a JSON schema for their payloads using the schema key. Ports with a schema annotate their IP objects automatically with the schema unless the IP object already has a specific schema
  • The previous type key of ports is now converted to the schema key. The schema of a port is available via the getSchema() method