Hello everybody,
A version of node-red-contrib-datdp-data-review
- Show beautiful object in node status
- Show string split by
\n
npm i @datdp88/node-red-contrib-datdp-data-review
Have fun with it,
DaTdP
Hello everybody,
A version of node-red-contrib-datdp-data-review
\n
npm i @datdp88/node-red-contrib-datdp-data-review
Have fun with it,
DaTdP
Hi @datdp,
Thanks for developing and sharing this node!!
I like it, because it can help me during developments of my nodes.
I didn't have a chance yet to test it, but I am wondering how it behaves when the message is large. For example when it contains a snapshot image from an IP camera. Do you truncate the message, or you show scrollbars, or ... ?
Bart
I have to be the boring person who points out node status was not intended for this.
As with all nodes the have customised their appearance in the editor, this node must be using internal APIs of the editor that could change at any time in a minor release and break the node.
Whilst we can't stop nodes choosing to do this, it would have been good to have had a discussion first.
Couldn't you just use a debug node?
When working on flow in Node-Red, I frequently use the node.status
. But node.status
not support multi line.
I can use node debug
, but it is not friendly with debugging multi nodes at the same time.
Logs in debug sidebar very long
You can, of course, filter that panel.
I would also point out that there are lots of threads showing various ways to output Node-RED logs in useful ways - I know that i've posted at least 3 different ways over the years including one recently using Node-RED's custom logging feature.
Having said that, I don't doubt there are uses for a node like this but, as Nick helpfully points out, really it would be best for this node to carry a warning to potential users because this is certainly not "node-red-like" in its approach
Oh, and one last thing - I happen to agree that I would occasionally like to be able to have >1 line in a status msg for clarity. So it might have been nicer to work with Nick to see if the debug node could have been updated in some way.
@datdp don't listen to the haters, your preview is very useful for my needs as well.
Can we get a link to your github project for this? I've got some ideas to improve it and would like to start from a fork of your code.
Sensible advice from the co-creator of NodeRed is hardly 'hate'.
Poorly coded/implemented add-ons can often cause other problems that take dev time to resolve.
So advice from the people that made and develop NodeRed really is generally good advice...