I would also like to bring back into focus a feature that was discussed in a 2022 forum thread: namely the ability to enable or disable a wire. In that discussion, it was mentioned that such a feature would require changes to the flow file format, which is why it was not pursued at the time. However, given its usefulness for debugging and maintaining complex flows, I would like to raise this request again and highlight its continued relevance.
Honestly that was going to be my recommendation, to put a disable node of sorts inbetween. I wonder - would be creating a passthrough node that could be disabled be a "good enough" solution in this case?
Hi @rko
I do hear what you are saying, and kind of feel your pain.
But I feel there is an easier solution.
So let's break down what you want to do.
You have two nodes connected with a wire and you want to disable it.
Now, there are two reasons I see for wanting to do this.
1 - you want to work on the node sending the message.
(or)
2 - you are wanting to isolate the receiving node as it will/could have more than 1 input wire.
So, my solution
For option 1:
Disable the node receiving the message/s.
(That is the easiest.)
For option 2:
The second node has multiple inputs and - I'm guessing you want to isolate other wires going to it.
So basically you disable the other nodes that are sending the messages.
I agree, I could just see the counterpoint that not having something named and clear would make managing complex flows annoying to some specific types of developers/users.
for extra bonus points, add a menu options "disable wire" that does those three steps in one!
EDIT: I'm not saying this is the perfect solution, especially as extra and unnecessary junction nodes are created, but it's a solution that works today.