Currently, users can add or remove tags from a node without conflict handling being considered. When two users change tags for a node, only the last update will be saved. The reason for that is that changing tags does not create a new version of a node.
Possible solution
Create a new version of the node when tags are changed. Only allow changing tags in a node update request by changing the tags property. This would force the user to provide the version when updating and allows us to check for conflicts in Mesh. The behavior would be similar to a node update request where a list of node references is changed.
Description
Currently, users can add or remove tags from a node without conflict handling being considered. When two users change tags for a node, only the last update will be saved. The reason for that is that changing tags does not create a new version of a node.
Possible solution
Create a new version of the node when tags are changed. Only allow changing tags in a node update request by changing the
tagsproperty. This would force the user to provide the version when updating and allows us to check for conflicts in Mesh. The behavior would be similar to a node update request where a list of node references is changed.