The version 1.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of noflo.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes1.0.0
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
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 1.0.0 of noflo was just published.
The version 1.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of noflo.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
1.0.0noflo.AsyncComponentclass -- use WirePattern or Process API insteadnoflo.ArrayPortclass -- use InPort/OutPort withaddressable: trueinsteadnoflo.Portclass -- use InPort/OutPort insteadnoflo.helpers.MapComponentfunction -- use WirePattern or Process API insteadnoflo.helpers.WirePatternlegacy mode -- now WirePattern always uses Process API internallynoflo.helpers.WirePatternsynchronous mode -- useasync: trueand callbacknoflo.helpers.MultiErrorfunction -- send errors via callback or error portnoflo.InPortprocess callback -- use Process APInoflo.InPorthandle callback -- use Process APInoflo.InPortreceive method -- use Process API getX methodsnoflo.InPortcontains method -- use Process API hasX methodsEXPORTSmechanism -- disambiguate with INPORT/OUTPORTscoped: falseon an outport will force all packets sent to that port to be unscopedCommits
The new version differs by 81 commits.
0a65a60Release 1.06af9928Merge pull request #574 from noflo/improve_legacy_detection0774c47Merge pull request #573 from noflo/greenkeeper/fbp-graph-0.3.00a4db51Add tests for legacy API detectionac5c435Don't shadow Splitfbe9db9Move inside the test4333d17fix(package): update fbp-graph to version 0.3.060a6bb6Mention legacy warningff6e014Merge pull request #572 from noflo/warn_legacybd3d5fdTreat old WirePattern as legacyb37ab85Subgraphs are not legacy4259bb2Simplify with isBrowser0cbe985Warn about components using legacy APIs180b462Link to the 1.0 prep blog post195fc5fMerge pull request #571 from noflo/greenkeeper/fbp-graph-0.2.0There are 81 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: