Re-fetch conversation after marking as read

Re-fetching makes sure that harder to compute values are re-fetched from
the server like unreadMessages, unreadMention, etc.

This introduces a new store action "fetchConversation".

Signed-off-by: Vincent Petry <vincent@nextcloud.com>

1 files changed, 7 insertions, 1 deletions

diff --git a/src/store/messagesStore.js b/src/store/messagesStore.js
index 6d8564de8..e618e4795 100644
--- a/src/store/messagesStore.js
+++ b/src/store/messagesStore.js
@@ -386,7 +386,7 @@ const actions = {
 	 * @param {bool} updateVisually whether to also update the marker visually in the UI;
 	 */
 	async updateLastReadMessage(context, { token, id = 0, updateVisually = false }) {
-		const conversation = Object.assign({}, context.getters.conversations[token])
+		const conversation = context.getters.conversations[token]
 		if (!conversation || conversation.lastReadMessage === id) {
 			return
 		}
@@ -400,7 +400,13 @@ const actions = {
 		if (updateVisually) {
 			context.commit('setVisualLastReadMessageId', { token, id })
 		}
+
 		await updateLastReadMessage(token, id)
+
+		if (updateVisually) {
+			// refetch to get more accurate values for unreadMessages, unreadMention, etc
+			context.dispatch('fetchConversation', { token })
+		}
 	},
 }