Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(federation): Mark notifications for federated rooms read similarly #11861

Conversation

nickvergessen
Copy link
Member

@nickvergessen nickvergessen commented Mar 19, 2024

πŸ› οΈ API Checklist

Following the pattern of normal chats we are marking read in getMessageContext() > waitForNewMessages() and receiveMessages() > waitForNewMessages()

Fix #11121

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not possible
  • πŸ“˜ API documentation in docs/ has been updated or is not required
  • πŸ”– Capability is added or not needed

Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
… end

Signed-off-by: Joas Schilling <coding@schilljs.com>
@nickvergessen nickvergessen merged commit b0e22ad into main Mar 19, 2024
64 checks passed
@nickvergessen nickvergessen deleted the bugfix/noid/mark-notifications-for-federated-rooms-also-read branch March 19, 2024 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review bug feature: api πŸ› οΈ OCS API for conversations, chats and participants feature: chat πŸ’¬ Chat and system messages feature: federation 🌐
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Notifications not removed from database after joining
3 participants