ZhenYi 047782e585 fix(room): handle reaction updates in onRoomMessage WS handler ... Root cause: publish_reaction_event sends a RoomMessageEvent (not reaction_added) with reactions field set. The onRoomMessage handler previously returned prev immediately when a duplicate ID was found, skipping the reaction update entirely. Fix: - Add reactions field to RoomMessagePayload so TypeScript knows it's there - When a duplicate message ID is found AND payload carries reactions, update the existing message's reactions field instead of ignoring - ReactionItem and ReactionGroup have identical shapes, so assignment works		2026-04-17 22:37:20 +08:00
..
storage	perf(room): prioritize IndexedDB cache for instant loads	2026-04-17 21:36:55 +08:00
api-error.ts	init	2026-04-15 09:08:09 +08:00
audio-utils.ts	init	2026-04-15 09:08:09 +08:00
diffUtils.ts	init	2026-04-15 09:08:09 +08:00
functionCallParser.ts	init	2026-04-15 09:08:09 +08:00
room-ws-client.ts	fix(room): add HTTP batch reactions endpoint and clean up dead code	2026-04-17 22:12:10 +08:00
room.ts	init	2026-04-15 09:08:09 +08:00
rsa.ts	init	2026-04-15 09:08:09 +08:00
seo.ts	init	2026-04-15 09:08:09 +08:00
timezone.ts	init	2026-04-15 09:08:09 +08:00
universal-ws.ts	init	2026-04-15 09:08:09 +08:00
utils.ts	init	2026-04-15 09:08:09 +08:00
validation.ts	init	2026-04-15 09:08:09 +08:00
ws-protocol.ts	fix(room): handle reaction updates in onRoomMessage WS handler	2026-04-17 22:37:20 +08:00
ws-token.ts	init	2026-04-15 09:08:09 +08:00