Issue with Delete & reconnect where flow loops back

[jbudd]

This is a simple flow to implement a queue.
An example of usage is for a batch SQL insert, where "Protracted processing" sends batches to the database. The queue ensures that the batches are inserted in the right order.

.

If you highlight limit and flush nodes, right click and "Delete & reconnect" (to remove the queue mechanism) it retains the loop back wire, an illegal connection from a node to itself.

[cymplecy]

I'd say that NR is doing what its been asked to do

[knolleary]

Technically there is nothing invalid with what it has done - it has removed the nodes as you've requested and maintained the connections that were there.

It is not 'illegal' to wire a node to itself; it's a valid thing to if, for example, your Function node is iterating over a list of items.

[jbudd]

@knolleary

it's a valid thing to if, for example, your Function node is iterating over a list of items.

But the editor will not permit wiring a node's output directly to it's own input.

I don't understand your example: to iterate over a list of items we have the for loop, etc.

[knolleary]

@jbudd

But the editor will not permit wiring a node's output directly to it's own input.

You are right - my mistake. Please raise an issue - we shouldn't have an editor action that allows you to get into that state.

[E1cid]

This was discuss before and we asked for this behaviour to remain , some of us use this behaviour and like to loop back without extra nodes.

Node left connected to itself via delete-selection-and-reconnect action