This suggestion may seem a bit odd, but please bear with me. I have a couple of projects that make heavy use of
node.status displays in the editor and status messages caught by
status nodes and shown in the dashboard. I have been looking for a way to generate arbitrary status messages in the middle of a flow. So far, only the
bigstatus nodes have worked for me, but both have drawbacks that would take too much space to describe here. The
change node has access to the flow and global context variables and the processing power of the JSONata language, so these features can be used "for free" in generating a status object. Only a couple of lines of code are needed to display the status (
msg.status), without (I believe) breaking existing flows. This may violate the "do one thing well" principle, but the
change node is already something of a "Swiss Army knife," and I think the feature would be useful. Any thoughts?