Block a user
REDCODE
pushed to feature/password-change-self-service at MilkyShots/MilkyShots
2026-07-10 08:32:20 +00:00
REDCODE
pushed to feature/password-change-self-service at MilkyShots/MilkyShots
2026-07-10 08:29:10 +00:00
REDCODE
pushed to feature/password-change-self-service at MilkyShots/MilkyShots
2026-07-10 08:23:29 +00:00
REDCODE
pushed to feature/password-change-self-service at MilkyShots/MilkyShots
2026-07-10 08:22:42 +00:00
REDCODE
pushed to feature/password-change-self-service at MilkyShots/MilkyShots
2026-07-10 08:15:27 +00:00
REDCODE
pushed to feature/password-change-self-service at MilkyShots/MilkyShots
2026-07-10 08:15:12 +00:00
REDCODE
created branch feature/password-change-self-service in MilkyShots/MilkyShots
2026-07-10 08:12:51 +00:00
REDCODE
pushed to feature/password-change-self-service at MilkyShots/MilkyShots
2026-07-10 08:12:51 +00:00
Remove auth check or reworking it into a heartbeat like answer
@Fastwind do we consider this done? After the rework that happened yesterday.
Home page should exclude deleted assets for all roles (including admin/curator)
A better approach would be to instantly integrate into the parameters of the GetAll a "Deleted", that would allow filtering deleted files in some way
refactor(auth): remove redundant SendWithRefreshAsync, enforce JwtTokenRefresher as sole handler
REDCODE
pushed to feature/remove-sendwithrefreshasync at MilkyShots/MilkyShots
2026-07-09 23:12:34 +00:00
REDCODE
created branch feature/remove-sendwithrefreshasync in MilkyShots/MilkyShots
2026-07-09 23:09:51 +00:00
REDCODE
pushed to feature/remove-sendwithrefreshasync at MilkyShots/MilkyShots
2026-07-09 23:09:51 +00:00
Fix User Deletion propagation
@Fastwind can correct me if I'm wrong, but users are to be soft deleted and no cascading should happen.