p1: prioritize mention browser notifications
All checks were successful
CI / test (push) Successful in 21s
All checks were successful
CI / test (push) Successful in 21s
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user