Sergey KozyrenkoandClaude Fable 5 9a5a8b53a5 fix(server): return 404 from name change when the user no longer exists ...

ChangeNameCurrentUser issued a bare UPDATE and ignored RowsAffected, so a stale
session for a deleted user got 200 — inconsistent with the email/password handlers
(which 404) and leaving the frontend's Users.NotFound mapping unreachable.

- check RowsAffected and return ErrUsersNotFound (404) when no row matched
- document the 404 in the swagger annotation
- add TestChangeNameCurrentUser (success, missing user, invalid name)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-06-14 10:35:52 +07:00

..

auth

…

context

…

docs

…

logger

…

models

fix(auth): accept mixed-case and long-TLD emails; normalize on change

2026-06-13 19:26:44 +07:00

oauth

…

rdb

…

response

feat(server): persist OAuth provider and add self-service name change

2026-06-13 02:56:15 +07:00

services

fix(server): return 404 from name change when the user no longer exists

2026-06-14 10:35:52 +07:00

middleware.go

…

router.go

feat(server): persist OAuth provider and add self-service name change

2026-06-13 02:56:15 +07:00

static_serving_test.go

…