Martin Brennan c908eeacc9 FIX: Update client lastReadMessageId on trashed message (#21697) ... Followup ae3231e140, when a message is trashed we already update the lastReadMessageId of all users in the channel to the latest non-deleted message on the server side. However we didn't propagate this to the client, so in some cases when we did the following: 1. Delete the last message in the channel 2. Switch to another channel 3. Switch back to the original We would get a 404 error from the target message ID being looked up still being the old lastReadMessageId (now deleted) for the user's channel membership. All we need to do is send the last not-deleted message ID for the channel (or thread) to all the member users.		2023-05-23 18:32:19 +02:00
..
controllers/chat	FIX: Page size check for thread messages (#21692)	2023-05-23 11:59:19 +02:00
helpers/chat	FEATURE: Mark all chat channels read with a shortcut (#20629)	2023-03-22 13:24:07 +10:00
jobs	FIX: Don't autojoin users when they have ready-only permissions (#20213)	2023-05-10 08:45:13 -03:00
models	FIX: Update client lastReadMessageId on trashed message (#21697)	2023-05-23 18:32:19 +02:00
queries/chat	DEV: Chat API channel#show changes for threading (#21632)	2023-05-22 13:59:46 +02:00
serializers/chat	DEV: Chat API channel#show changes for threading (#21632)	2023-05-22 13:59:46 +02:00
services	FIX: Update client lastReadMessageId on trashed message (#21697)	2023-05-23 18:32:19 +02:00
validators/chat	DEV: properly namespace chat (#20690)	2023-03-17 14:24:38 +01:00
views