You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(conversations): this fixes the behavior described in #11882: system messages like user added or removed, moderator promoted or demoted trigger an activity bump of the conversation in the list and move it to the top. This fix keeps activity bumps for real chat messages but won't bump the activity anymore for the aforementioned system messages. This fix also incorporates use of the new lastMetadataActivity field to update this information instead of lastActivity accordingly and can be expanded later on to handle other kind of messages differently. No changes client side are needed.
Signed-off-by: Christian Lorang <madcatcl2@gmx.de>
>>>>>>> a798ce9366 (change(conversations): change behavior in all necessary places for Rooms and Threads to use / set lastMetadataActivity instaed of lastActivity where appropriate, i.e. where system messages are signalled and not real chat messages.)
63
+
64
+
>>>>>>> 2ed52550f0 (feature(api): Add a newfieldand corresponding functionality for lastMetadaActivity for Rooms and Threads, similar to lastActivity. This also adds a database migration for the oc_talk_rooms and oc_talk_threads tables as well. Functions are introduced and prepared for later use. The use of the field lastActivity to signal when the last real message in a conversation appeared remains unchanged to keep the API stable. The intended use of this feature is to better distinguish between real messages (lastActivity) to notify and bump conversations in the thread list to the top, and other status / metadata related messages (lastMetadataActivity) like room state and participant list changes that shall get synced and be updated in the clients, but not trigger an activity bump of its conversations in the thread list.)
65
+
}
66
+
67
+
$table = $schema->getTable('talk_threads');
68
+
51
69
if (!$table->hasColumn('last_metadata_activity')) {
>>>>>>> a798ce9366 (change(conversations): change behavior in all necessary places for Rooms and Threads to use / set lastMetadataActivity instaed of lastActivity where appropriate, i.e. where system messages are signalled and not real chat messages.)
68
90
$update = $this->connection->getQueryBuilder();
69
91
$update->update('talk_rooms')
70
92
->set('last_metadata_activity', 'last_activity');
@@ -73,6 +95,15 @@ public function postSchemaChange(IOutput $output, \Closure $schemaClosure, array
73
95
$update->update('talk_threads')
74
96
->set('last_metadata_activity', 'last_activity');
75
97
$update->executeStatement();
98
+
<<<<<<< HEAD
99
+
=======
100
+
$update = $this->connection->getQueryBuilder();
101
+
$update->update('talk_rooms')
102
+
->set('last_metadata_activity', 'last_activity');
103
+
$update->executeStatement();
104
+
>>>>>>> 2ed52550f0 (feature(api): Add a newfieldand corresponding functionality for lastMetadaActivity for Rooms and Threads, similar to lastActivity. This also adds a database migration for the oc_talk_rooms and oc_talk_threads tables as well. Functions are introduced and prepared for later use. The use of the field lastActivity to signal when the last real message in a conversation appeared remains unchanged to keep the API stable. The intended use of this feature is to better distinguish between real messages (lastActivity) to notify and bump conversations in the thread list to the top, and other status / metadata related messages (lastMetadataActivity) like room state and participant list changes that shall get synced and be updated in the clients, but not trigger an activity bump of its conversations in the thread list.)
105
+
=======
106
+
>>>>>>> a798ce9366 (change(conversations): change behavior in all necessary places for Rooms and Threads to use / set lastMetadataActivity instaed of lastActivity where appropriate, i.e. where system messages are signalled and not real chat messages.)
0 commit comments