p1: prioritize mention browser notifications
All checks were successful
CI / test (push) Successful in 21s

This commit is contained in:
2026-03-08 14:06:02 +03:00
parent f670305073
commit 539ba70294
2 changed files with 15 additions and 6 deletions

View File

@@ -238,4 +238,6 @@ Validation/runtime error during WS processing:
- On `chat_updated`, refresh chat metadata via REST (`GET /api/v1/chats` or `GET /api/v1/chats/{chat_id}`).
- On reconnect/visibility restore, reconcile state by reloading already-opened chats/messages via REST
to recover missed `message_deleted`/delivery updates after transient disconnects or backend restarts.
- For browser notifications, mentions (`@username`) should be treated as high-priority and can bypass
per-chat-type notification toggles in client preferences.
- Use REST message history endpoints for pagination; WS is realtime transport, not history source.