node.status question

[Mike Bell]

All,

I often use the node.status function when debugging function nodes. If after debugging, I remove the node.status call and re-deploy the node, it continues to display its most recent status. The only way I have found to remove the display is to replace the the function call with node.status({}), execute the function, edit the node again to remove the function call, and execute the function yet again. It seems to me that when a function node has been modified, the editor should clear its status display until the next time it is executed. I grant that there might be times when it would be useful for a function node to display its status from the previous execution, but if it has just been edited, I suspect that these cases would be the exception. Is there an obvious reason why the editor should or must behave the way it does?

Regards,

Mike

[Dave C-J]

Indeed - I can't think of a good reason to leave the status around after a new deploy, as they will be "undetermined" until positively set to a known good value, so flushing them makes sense to me.