Deleting a Middle Node leads to all other connectors getting removed from view

I was using the example from dev folder. Delete option was added to NodeType2 in this demo. Instead of adding NodeType2 as the last node ( as given in example ), I added it as a middle node by changing the connections source and target in data.ts file. On deleting the node, the connections are not removed from view or not deleted in few scenarios. @ajainarayanan

Steps to Reproduce issue: Replace the data.ts with the data below. Delete node ( Node Type 2 (action 1) ), add a new node of any type. All the existing connections are removed from view.

export const data = {
  connections: [
    {
      sourceId: "1",
      targetId: "2",
    },
    {
      sourceId: "2",
      targetId: "3",
    },
    {
      sourceId: "2",
      targetId: "4",
    },
    {
      sourceId: "3",
      targetId: "4",
    },
    {
      sourceId: "3",
      targetId: "5",
    },
    {
      sourceId: "4",
      targetId: "5",
    },
  ],
  nodes: [
    {
      config: {
        label: "Default Node",
        type: "source",
      },
      id: "1",
    },
    {
      config: {
        label: "Node Type 1 (action)",
        type: "action",
      },
      id: "2",
    },
    {
      config: {
        label: "Node Type 1 (action)",
        type: "action",
      },
      id: "3",
    },
    {
      config: {
        label: "Node Type 2",
        type: "action",
      },
      id: "4",
    },
    {
      config: {
        label: "Node Type 2",
        type: "action",
      },
      id: "5",
    },
  ],
};

[etherealm13]

@ajainarayanan This works. Closing the issue. Thanks.

[etherealm13]

Can you check the line no. 54 of connectionReducers.ts ?

  if (sourceNode.config.type === 'action' && connObj.sourceId.indexOf('-DottedEndpoint-right') !== -1) {
    newConnObj.sourceId = `${connObj.sourceId.slice(
      0,
      connObj.sourceId.indexOf('-DottedEndpoint-right')
    )}`;
  }
  return newConnObj;
};

Instead of finding the indexOf(“-right”), it should be as above. This fixes the issue. @ajainarayanan