Organizations: join and leave #81

Activity

1. Adron

   added

   parityClosing a gap against interlinedlist.comClosing a gap against interlinedlist.com

   P3Niche or minorNiche or minor

   area:organizationsOrganizationsOrganizations

   on Sep 15, 2026
2. Adron

   added a parent issue on Sep 15, 2026

   • Organizations parity gaps #80
3. Adron commented on Sep 16, 2026

   

   Adron

   on Sep 16, 2026

   MemberAuthor

   More actions

   Implemented in #109 (branch issue/81-org-join-leave). Closing here — review and any follow-up happens on the PR.

   The open question in this issue is answered: POST /api/user/organizations is join, not create-under-user. Body is {"organizationId":"<id>"}, returns 201 {"message":"Joined organization successfully","membership":{…}}, with 409 conflict when already a member.

   There is no dedicated leave endpoint. Leaving is expressed as removing your own membership via DELETE /api/organizations/{id}/members/{yourUserId}. That works, but it means leave depends on SessionStore.userId being present — worth confirming whether a DELETE /api/user/organizations/{id} exists or is planned, since a members/me route would be sturdier.

   Last-owner behaviour confirmed live: the server returns 400 {"error":"Cannot remove the last owner","code":"bad_request"}. The UI detects the case client-side and explains it without offering a destructive action, falling back to mapping that exact server error to the same explanation.

   Also fixed along the way: GET /api/organizations/{id} reports membership as userRole, never role — the existing DTO read only role, so the detail screen's role was always null. And GET /api/organizations/{id}/members is members-only (403), so that request is now skipped for non-members rather than surfacing a permission error.

   Note for #83: the detail overflow still offers Edit/Delete to non-members. Membership is now known, so gating them is a small change — but it is roles/visibility work, so it was left there.
4. Adron

   closed this as completedon Sep 16, 2026
5. Adron

   added a commit that references this issue on Sep 16, 2026

   merge: #81 organization join/leave (PR #109)

   68b3a36