Skip to content

mm-chat: Emit "changed" after unread is completely set

Mohammed Sadiq requested to merge mohammed.sadiq/chatty:wip/sadiq/fix-notification-reset into master

When the signal is emitted, all callback handlers are run immediately. And so, if the callback sets unread count to zero, it's not actually saved properly to db as the previous change to db is commited after the callbacks are run.

Fix it by emitting the signal after all changes are commited

Fixes #689 (closed)

Merge request reports