refactor: improve message content filtering and update dependencies in new chat

- Enhanced the message content filtering logic to exclude both "thinking-steps" and "mentioned-documents" for better clarity in chat messages.
- Updated the dependency imports in the thread component for improved organization and consistency.
- Adjusted the effect dependencies in the NewChatPage component to include the message documents map for better state management.
This commit is contained in:
Anish Sarkar 2025-12-23 16:04:39 +05:30
parent 6f330e7b8d
commit 1d646d3b5f
2 changed files with 14 additions and 39 deletions

View file

@ -77,15 +77,12 @@ function convertToThreadMessage(msg: MessageRecord): ThreadMessageLike {
content = [{ type: "text", text: msg.content }];
} else if (Array.isArray(msg.content)) {
// Filter out custom metadata parts - they're handled separately
const filteredContent = msg.content.filter(
(part: unknown) =>
!(
typeof part === "object" &&
part !== null &&
"type" in part &&
(part as { type: string }).type === "thinking-steps"
)
);
const filteredContent = msg.content.filter((part: unknown) => {
if (typeof part !== "object" || part === null || !("type" in part)) return true;
const partType = (part as { type: string }).type;
// Filter out thinking-steps and mentioned-documents
return partType !== "thinking-steps" && partType !== "mentioned-documents";
});
content =
filteredContent.length > 0
? (filteredContent as ThreadMessageLike["content"])
@ -219,7 +216,7 @@ export default function NewChatPage() {
} finally {
setIsInitializing(false);
}
}, [urlChatId, searchSpaceId, router]);
}, [urlChatId, searchSpaceId, router, setMessageDocumentsMap]);
// Initialize on mount
useEffect(() => {