- Additional example flow included for testing multi-level out and return.
- Change return node so that topic setting doesn't override the msg.topic. The topic setting in the node will now only be used if the inbound msg has no topic.
- Previous example flows updated.
-
msg._eventOriginator
andmsg._eventReturner
are now both arrays with the latest entries at the top. This enables multi-level out and return.Infinite loops should no longer be possible unless you deliberately mess with these properties (hint: don't!).
-
event-return
node. Allows event-based sub-flows or loops.Change an
event-out
node to allow output from anevent-return
node.Then create a flow starting with an
event-in
node, do some processing and end with anevent-return
node.The
event-return
node does not need any configuration, it uses themsg._eventOriginator
property from the input msg to route data back to the originatingevent-out
using an internal event sender/listener based on the node ID of theevent-out
node.You can, however, allow the node to pass messages through to an output if you want to.
You can also override the msg.topic for the output if you wish.
-
New example added that shows (and tests) the use of the
event-return
node.
-
Removed global variable.
-
Moved the event handler to an external module ti-common-event-handler
This module will be used by other packages including node-red-contrib-uibuilder to provide a common event handler.