feat(admin): add reactivation affordance + endpoint for suspended users #157

Merged

David merged 2 commits from feat/BUNYIP-120-admin-user-reactivate into main

2026-06-17 12:46:37 +02:00

David commented

2026-06-17 03:32:00 +02:00

Owner

Admin user suspension was one-way: suspended (soft-deleted) accounts vanished from the admin list and detail page (both filter deleted_at IS NULL), so there was no Reactivate button and no reachable path to set active=true, even though the bunyip-api status endpoint already handled the reactivate direction (the stale bunyip-web comment claiming the backend rejects active=true and needs a new endpoint was wrong).

UserRepository::list_paginated gains an active: Option<bool> selector: the default (None/Some(true)) still lists live accounts, Some(false) lists soft-deleted ones. The admin list handler forwards a new active query param so the bunyip-api /admin/users endpoint can return the suspended set.

bunyip-web exposes this as an Active/Suspended toggle on the users page. The Suspended view tags each row and offers a single Reactivate action wired to a new /admin/users/:id/reactivate route, which PUTs active=true to the status endpoint; reactivation returns the admin to the Suspended view.

#BUNYIP-120

Admin user suspension was one-way: suspended (soft-deleted) accounts vanished from the admin list and detail page (both filter `deleted_at IS NULL`), so there was no Reactivate button and no reachable path to set `active=true`, even though the bunyip-api status endpoint already handled the reactivate direction (the stale bunyip-web comment claiming the backend rejects active=true and needs a new endpoint was wrong). `UserRepository::list_paginated` gains an `active: Option<bool>` selector: the default (`None`/`Some(true)`) still lists live accounts, `Some(false)` lists soft-deleted ones. The admin list handler forwards a new `active` query param so the bunyip-api `/admin/users` endpoint can return the suspended set. bunyip-web exposes this as an Active/Suspended toggle on the users page. The Suspended view tags each row and offers a single Reactivate action wired to a new `/admin/users/:id/reactivate` route, which PUTs `active=true` to the status endpoint; reactivation returns the admin to the Suspended view. #BUNYIP-120

David added 1 commit

2026-06-17 03:32:00 +02:00

feat(admin): add reactivation affordance + endpoint for suspended users

Check / fmt / clippy / build / test (pull_request) Successful in 1m58s

Details

acce4f900f

Admin user suspension was one-way: suspended (soft-deleted) accounts vanished from the admin list and detail page (both filter `deleted_at IS NULL`), so there was no Reactivate button and no reachable path to set `active=true`, even though the bunyip-api status endpoint already handled the reactivate direction (the stale bunyip-web comment claiming the backend rejects active=true and needs a new endpoint was wrong).

`UserRepository::list_paginated` gains an `active: Option<bool>` selector: the default (`None`/`Some(true)`) still lists live accounts, `Some(false)` lists soft-deleted ones. The admin list handler forwards a new `active` query param so the bunyip-api `/admin/users` endpoint can return the suspended set.

bunyip-web exposes this as an Active/Suspended toggle on the users page. The Suspended view tags each row and offers a single Reactivate action wired to a new `/admin/users/:id/reactivate` route, which PUTs `active=true` to the status endpoint; reactivation returns the admin to the Suspended view.

#BUNYIP-120

David added 1 commit

2026-06-17 12:46:33 +02:00

Merge branch 'main' into feat/BUNYIP-120-admin-user-reactivate

Create release / Create release from merged PR (pull_request) Has been skipped

Details

Check / fmt / clippy / build / test (pull_request) Failing after 16s

Details

c8e2416690