Browse Source
Two issues found while reviewing the previous commits: The bulk endpoint unwrapped the client supplied member id, so a single entry without an id took the whole request down with a 500 and silently dropped the confirmations of every other entry in the same call. Skip such an entry instead. The manual `bulk_confirm_invite` has the same unwrap, that one is left alone here. `send_invite` announced the pending member right after saving the membership, which is before the collections and groups of the invite are attached. An admin client acts on that notification immediately, so it could confirm the member while its access was still incomplete, and a failing collection or group assignment would leave a confirmed member behind. The notification now happens once the invite is fully applied.pull/7499/head
1 changed files with 10 additions and 4 deletions
Loading…
Reference in new issue