Spurious group membership change notifications #12
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To add (or in theory, remove) users to a group, one needs to set the new complete list of members in a
PUT
call, as there is noPATCH
support. The way this is implemented results in a notification being sent to every group member, saying that they have been removed from the group, and then that they have been added to the group, even though nothing really changed for them. I can see how this happens, with the code first removing everyone from the group and then re-adding from the new list, but it's not very nice.Hi! Thanks for your report.
This sounds like normal behavior from Nextcloud and only a side effect of how we deal with membership updates. I agree it's not nice though.
Anyway, we will look into it and come back to you.
Right. A different implementation of the membership update, which only changes users that require change, might avoid this. But this is more of a nuisance than a problem.
I haven't looked at the code but implementing a diffing logic server-side is probably the way to go.
Should be fixed in
362ab2b4c1
.