bergie
commented
7 years ago Note: this version of noflo-objects changes behavior of components like GetObjectKeys and SetPropertyValues in way that the property name needs to be send for each execution. Example of how to deal with this:
https://github.com/noflo/noflo-yaml/commit/efd61693cee0c33ac85b894f0a244532d3b20b33
Version 0.3.0 of noflo-objects just got published.
The version 0.3.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of noflo-objects. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 58 commits .
f5e54c3Bump out of beta5aec913Merge pull request #103 from trustmaster/master38375a3Merge branch 'master' of github.com:noflo/noflo-objectse90bd0bFix invalid SetPropertyValue value handlingda53819Merge pull request #102 from trustmaster/masterfc0cc27Add ip.clonable check to RemovePropertyc5cd2beFix specsd758195Fix Values93a6a0dFix UniqueArray spec399be99Fix SplitObject34a70daFix SplitArray7e28ddbFix SliceArrayefaa97fFix Size spec26a4c17Fix SimplifyObjectba8678dFix SetPropertyValueThere are 58 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: