Right now only the DeleteNode response is generated even if the node had connections. Would expect it to generate a disconnect event for every connection it had.
Indeed! This was an oversight on my end. I just pushed a new PR that fixes it. I verified the new behavior is correct, but could you give it a go on your end to verify everything now works as intended?
Right now only the DeleteNode response is generated even if the node had connections. Would expect it to generate a disconnect event for every connection it had.