Open michaelblight opened 4 years ago
Haha came back lloking for this issue almost exactly two years later and found I already raised it. This is now a bigger problem with "link call" as the return link is lost. You can probably copy the value into origPayload, and copy it back out after, but you shouldn't have to.
EDIT: Looking into the code, the problem is line 254 sends a brand new message. If you tell it to send an array instead, it will send clonedMsg (where payload is now an array), which still has msg._linkSource
and anything else from the input message.
Before logging an issue, please make sure that you are using latest version on npm. If you are testing a development version (@next on npm or the version on GitHub), please make sure that you let me know as well.
Please ensure that as much of the following information is included as possible:
Software and Package Versions
How is Node-RED installed? Where is uibuilder installed?
The official docker image
I'm using
fs-file-lister
in a flow where maintaining the existing message is important. However, this node clones the message, which "breaks" my flow. It would be helpful if this node did not clone, or at least had the option to not clone.