You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When "move" and "copy" jsonpatch operations are considered, two operations could conflict even if the "patch" members are not the same. If a copy operation is from "/foo" to "/bar" and there's a remove "/foo" operation as well, those two are in conflict even though they don't have the same path. The outcome will differ depending on the order of patch application. Similarly, a move and replace operation could be in conflict when the move "from" is equal to the replace "path".
One way to resolve this would be to consider "move" and "copy" operations as having two path elements, and they would conflict with any other operation containing either one of these as path elements (either as an "path" on any operation, or as a "from" field in another move or copy operation.
The text was updated successfully, but these errors were encountered:
When "move" and "copy" jsonpatch operations are considered, two operations could conflict even if the "patch" members are not the same. If a copy operation is from "/foo" to "/bar" and there's a remove "/foo" operation as well, those two are in conflict even though they don't have the same path. The outcome will differ depending on the order of patch application. Similarly, a move and replace operation could be in conflict when the move "from" is equal to the replace "path".
One way to resolve this would be to consider "move" and "copy" operations as having two path elements, and they would conflict with any other operation containing either one of these as path elements (either as an "path" on any operation, or as a "from" field in another move or copy operation.
The text was updated successfully, but these errors were encountered: