Releases: ollixx/node-red-contrib-components
v0.4.0-rc.2
Release candidate for v0.4.0-rc.2.
Published from the tagged commit on master to the npm next dist-tag.
Install for validation with:
npm install node-red-contrib-components@next
v0.4.0-rc.1
Release candidate v0.4.0-rc.1 published to the npm next dist-tag.\n\nNote: This RC was created before the release workflow was hardened to require tagged commits from master. A follow-up RC from master should supersede it before the final 0.4.0 release.
Release 0.3.6
use evaluateNodeProperty callback for Node-RED 3.5.x/4.x compatibility
Version 0.3.4
Version 0.3.2
Refactoring of the context feature.
BREAKING CHANGE again.
release 0.2.3 was a breaking change and made old flows not work.
After a user request I decided to make the context feature optional.
A component can be made "using the context" feature and set each parameter to local, once the feature is enabled.
The Release also has quite some bugfixes regarding the editor and validation of connectivity. There should be less red triangles top be seen.
Version 0.2.2
#Maintenance Release
Fixes
- RUN node: API list is updated after a change of the selected target component
- RUN node: API list: minor layout changes
Changes
- Added a Jump-To link to the Editor of the RUN node, that focuses on the matching START node.
- Selection in RUN node Editor shows "empty selection" option, until a component was selected
- split files for each node.
Version 0.20
Feature/improvements 0.2.0
- global flag for API Parameters
- global flag, fix: find nodes, fix validation
- fix find nodes, msg.component, fix broadcast, fix in-only, separate events
- cleanup, examples: recursion, broadcast, in-only
- more examples
- small refinement for clean examples
- refined README
Version 0.1.19 Bugfix
Hotfix to prevent unwanted "return chains". It was possible for more than the intended RUN node to handle a return event under certain circumstances. This fixed.
The problem occurred only in complex scenarios with many nested components.
Version 0.1.18
Hotfix for a problem introduced with 0.1.17 in findReturnNodes().
Version 0.1.17
Bugfix for issue #27