Feature request: Attach debug node to the IN connector on a node

Core Development Feature Requests
21

No, unfortunately not yet. As I developed it mainly during work hours, I need to get permission from the superiors.

Our developer team is rather small, so "officially" maintaining open source projects is a matter of resources. But personally, I would really like to share some of the stuff and give it back to the community. My plan is to open-source it as a personal project once that is resolved. :slightly_smiling_face:

4 Likes
22

Well, after reading this thread and checking out some other pages. I came up with a solution. A simple passthrough subflow-node thingy. It is simply a subflow with one input and one output and passes through any msg object as is and outputs the object to the debug tab.

Here's my solution. Modify as you wish. This'll kinda do the trick for me, I guess.

[
    {
        "id": "c2bcad1.0c3e4d",
        "type": "subflow",
        "name": "Inline Debug",
        "info": "",
        "category": "",
        "in": [
            {
                "x": 160,
                "y": 180,
                "wires": [
                    {
                        "id": "bd6896fe.f4e21"
                    }
                ]
            }
        ],
        "out": [
            {
                "x": 480,
                "y": 180,
                "wires": [
                    {
                        "id": "bd6896fe.f4e21",
                        "port": 0
                    }
                ]
            }
        ],
        "env": [],
        "icon": "node-red/debug.png"
    },
    {
        "id": "bd6896fe.f4e21",
        "type": "function",
        "z": "c2bcad1.0c3e4d",
        "name": "",
        "func": "node.warn(msg);\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 310,
        "y": 180,
        "wires": [
            []
        ]
    },
    {
        "id": "b87aeaf7.af81f",
        "type": "subflow:c2bcad1.0c3e4d",
        "z": "c5627bb2.08bf88",
        "name": "",
        "x": 590,
        "y": 240,
        "wires": [
            [
                "253e234.f55eb5c"
            ]
        ]
    }
]
4 Likes
23

What a brilliantly simple idea :slight_smile:

24

I had a quick look at it.

Just one thing though:
How do you turn it off so you don't see the output?

Why:
Well, I get that you need debug nodes when making flows.
But once they are working, getting outputs is introducing overheads which may not be wanted/needed.
Deleting the nodes could be painful.

My way around the problem is using the FAN node.
(yeah, an empty function node could work too. But the advantage with the fan node is that it is green, and you know it isn't simply an empty function node.)

So my flows (where needed) look something like this:

Screenshot%20from%202019-08-25%2009-36-14
Screenshot from 2019-08-25 09-36-14.png747Ɨ351 33 KB

25

I added some stuff. to enable and disable the output and change the output from the msg object to just the payload. Now I'm having a whole new problem.

26

And the complete(ish) solution.

Be gentle.

1 Like