David Battersby 79ececd976 FIX: handle thread participants limit on the frontend (#23839) ... Workaround for an issue we are experiencing on thread index frontend where thread loads participants correctly (up to 10), then refreshes the threads and then limits to 3 participants. There is an issue with storing threads for the main channel view and the thread list in the same store so handling the max participants on the frontend is a workaround until channel.threadsManager is updated. I've adjusted the tests to handle the additional data being returned from ThreadParticipantQuery.		2023-10-09 14:04:59 +08:00
..
controllers/chat	DEV: removes the notion of staged thread (#23612)	2023-09-15 18:09:45 +02:00
helpers/chat	FEATURE: Mark all chat channels read with a shortcut (#20629)	2023-03-22 13:24:07 +10:00
jobs	FEATURE: Link chat notifications directly to message (#23617)	2023-09-16 20:37:35 +01:00
models	FIX: ensures an empty last message won't cause errors (#23647)	2023-09-25 12:43:04 +02:00
policies	DEV: Migrate Chat::MessageCreator to a service (#22390)	2023-09-07 08:57:29 +02:00
queries/chat	FIX: handle thread participants limit on the frontend (#23839)	2023-10-09 14:04:59 +08:00
serializers/chat	FIX: ensures an empty last message won't cause errors (#23647)	2023-09-25 12:43:04 +02:00
services	FIX: handle thread participants limit on the frontend (#23839)	2023-10-09 14:04:59 +08:00
validators/chat	DEV: properly namespace chat (#20690)	2023-03-17 14:24:38 +01:00
views