Remove the option to update edges in node-update operations

[hartig]

Currently, it is possible to update the (outgoing) edges of a node within the corresponding node-update operation. For instance, it is possible to do the following.

mutation {
   updateBlogger( id: "56565", data: {
      name: "Robert",
      blogs: [
         { connect: "41" },
         { connect: "21" }
      ]
   } ) {
      id
   }
}

What this does is to remove (!) all existing edges from blogger 56565 to blogs and replace them by two new edges that connect the blogger to blogs 41 and 21, respectively. This behavior is not very intuitive and may cause a lot of confusion, and it is also problematic in terms of the automatically maintained lastUpdateDate field (as discussed in #63).

I also do not see any other way of defining a more intuitive behavior for this.

Consequently, I am proposing to remove this option altogether. Edges can still be added by the edge-creation operations and removing them, as well as updating their annotations will become available as per #36 and #35, respectively.

@keski @epii-1 Any opinions?

[hartig]

In today's call we agreed to my proposal to remove this option.

@epii-1 can you please implement this decision.

[hartig]

@epii-1 sorry, I was too fast! This decision should not be implemented right away. As I said in the call, from the SPIRIT perspective, this change needs to be handled carefully. Therefore, let's not do anything in the code for now. Instead, I will bring this to the attention of the other partners and will make sure that they have all modified their client code to use the edge-related operations instead. Only once this is done, we should implement this decision. So, for the moment, we simply keep this issue here as a reminder.