test 4_11 that is testing the update-update ordered feature variant (ii)
"The predecessor or successor of an inserted value is concurrently deleted"
Example:
User 2 inserts a new value B after A; this value, however, A has been concurrently deleted by user 1. Thus, a conflict is reported
This should be tightly coupled to successor, predecessor
Problem:
Since we using Json Pointer its not out of the box to get successor, predecessor, this has to a part comes from semantic information (?) or we have to split path from json pointer get the last elem if its index, compare added and deleted but with index+1 /-1 ... ... and all that kind of messy stuff
test 4_11 that is testing the update-update ordered feature variant (ii)
"The predecessor or successor of an inserted value is concurrently deleted"
Example:
User 2 inserts a new value B after A; this value, however, A has been concurrently deleted by user 1. Thus, a conflict is reported
This should be tightly coupled to successor, predecessor
Problem:
Since we using Json Pointer its not out of the box to get successor, predecessor, this has to a part comes from semantic information (?) or we have to split path from json pointer get the last elem if its index, compare added and deleted but with index+1 /-1 ... ... and all that kind of messy stuff