fix(conversation): Skip last message update when adding or removing participants by sudormant · Pull Request #18657 · nextcloud/spreed

fix(conversations): set default shouldSkipLastActivity / skipLastActivity flag for event dispatcher from false to true. This should help with chat state changes (users removed / added, moderators p…

sudormant

committed

b82d0f7

feature(api): Add a new field and corresponding functionality for lastMetadaActivity for Rooms and Threads, similar to lastActivity. This also adds a database migration for the oc_talk_rooms and oc…

sudormant

committed

996987f

documentation: clarify that sorting by lastActivity in the thread list will still go by last message activity, after introducing lastMetadataActivity, and not sort by last metadata changes in rooms…

sudormant

committed

e3c2a0e

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 sign…

sudormant

committed

686660f

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 a…

sudormant

committed

7edf49c

chore: fix git merge gone wrong

sudormant

committed

3bc6cb7

refactor(conversations): limit no acitvity bumping by metadata changes only to rooms, remove same handling from threads

sudormant

committed

ea9822a

fix(conversations): add getter / setter for shouldSkipLastActivity/MessageUpdate to be compatible with another pull request making this field private

sudormant

committed

d6ebb3d

fix(conversations): fix handling events that don't have a last message (like room creation) when deciding whether to bump activity

sudormant

committed

6efaea7

fix: Update lib/ResponseDefinitions.php

sudormant

and

nickvergessen

committed

0796b28

fix(conversations): reworked merge request scope as discussed in issue comments

sudormant

committed

e5ffb30

fix(conversations): rework merge request scope as discussed in issue comments

sudormant

committed

4dd48b0

fix: further changing of messange / activity bumping handling and tests

sudormant

committed

a2ba219

Navigation Menu

fix(conversation): Skip last message update when adding or removing participants - #18657

fix(conversation): Skip last message update when adding or removing participants#18657
sudormant wants to merge 13 commits into
mainfrom
bugfix/11882/skipLastMessage

Commits on Jul 23, 2026

fix(conversations): set default shouldSkipLastActivity / skipLastActivity flag for event dispatcher from false to true. This should help with chat state changes (users removed / added, moderators p…

feature(api): Add a new field and corresponding functionality for lastMetadaActivity for Rooms and Threads, similar to lastActivity. This also adds a database migration for the oc_talk_rooms and oc…

documentation: clarify that sorting by lastActivity in the thread list will still go by last message activity, after introducing lastMetadataActivity, and not sort by last metadata changes in rooms…

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 sign…

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 a…

chore: fix git merge gone wrong

refactor(conversations): limit no acitvity bumping by metadata changes only to rooms, remove same handling from threads

fix(conversations): add getter / setter for shouldSkipLastActivity/MessageUpdate to be compatible with another pull request making this field private

fix(conversations): fix handling events that don't have a last message (like room creation) when deciding whether to bump activity

fix: Update lib/ResponseDefinitions.php

fix(conversations): reworked merge request scope as discussed in issue comments

fix(conversations): rework merge request scope as discussed in issue comments

fix: further changing of messange / activity bumping handling and tests