From 4aedf5fd62d002f02369390f3f5613a308ec4eaf Mon Sep 17 00:00:00 2001 From: wizardchen Date: Mon, 18 May 2026 11:28:08 +0800 Subject: [PATCH] fix(chat): simplify enableMemoryOverride assignment in sendMsg function Refactored the assignment of enableMemoryOverride in the sendMsg function to remove explicit type declaration, enhancing code clarity. This change maintains the existing functionality while streamlining the code structure. --- frontend/src/views/chat/index.vue | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend/src/views/chat/index.vue b/frontend/src/views/chat/index.vue index d97724e7..15e64d09 100644 --- a/frontend/src/views/chat/index.vue +++ b/frontend/src/views/chat/index.vue @@ -556,7 +556,7 @@ const sendMsg = async (value, modelId = '', mentionedItems = [], imageFiles = [] // field unset so the backend reads `user.preferences.enable_memory`; // for embedded widgets we still send an explicit `false` so a user's // personal "memory on" setting doesn't leak into a KB-embed context. - const enableMemoryOverride: boolean | undefined = props.embeddedMode ? false : undefined; + const enableMemoryOverride = props.embeddedMode ? false : undefined; // Get knowledge_base_ids from settings store (selected by user via KnowledgeBaseSelector) // Merge @mentioned KB/file IDs so retrieval uses the same targets user @mentioned (including shared KBs)