fusion/.changeset/fix-chat-view-message-truncation.md at 9bea9510c04d7f6359cda2ee7da7688f35c37c05

Files

Josemi Liebana 64056b380d fix(dashboard): load all messages in chat on initial open (useChat + useQuickChat)

Both useChat (full ChatView) and useQuickChat (FAB) loaded only the first 50
messages on open and never paginated further. In useChat, loadMoreMessages
exists but ChatView never calls it — dead code. In useQuickChat, there was
no pagination at all.

Fix: add fetchAllMessagesInChat / fetchAllMessages helpers (paginate through
the API 200-msg cap), replace all limit:50 initial-load call sites, and
add stale-session guards via activeSessionRef before calling setMessages.
hasMoreMessages is set to false after a full initial load.

Forward-pagination path in useChat (isPaginationRequest=true) is preserved
for backward compat.

2026-05-22 14:51:46 +02:00

662 B

Raw Blame History

@runfusion/fusion

@runfusion/fusion
patch

Fix useChat truncating sessions longer than 50 messages on initial open.

loadMessages() fetched { limit: 50 } for the initial load. The loadMoreMessages callback was never called from ChatView (no scroll sentinel exists), so sessions beyond 50 messages were permanently cut off.

Fix: introduce fetchAllMessagesInChat() that paginates through the API's 200-message cap and replace the initial load path. A stale-session guard (via activeSessionRef) prevents overwriting a switched session's messages. The forward-pagination path (isPaginationRequest = true) is preserved unchanged for backward compatibility.

662 B Raw Blame History

662 B

Raw Blame History