adai/MemoryBear
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(web): the memoryContent field is compatible with numbers and strings

Browse Source
This commit is contained in:
zhaoying
2026-01-30 12:19:23 +08:00
parent 102712a16e
commit 88ab86734d
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
web/src/views/ApplicationConfig/Agent.tsx
View File

@@ -126,12 +126,16 @@ const Agent = forwardRef<AgentRef>((_props, ref) => {
getApplicationConfig(id as string).then(res => { getApplicationConfig(id as string).then(res => {
const response = res as Config const response = res as Config
let allTools = Array.isArray(response.tools) ? response.tools : [] let allTools = Array.isArray(response.tools) ? response.tools : []
const memoryContent = response.memory?.memory_content
const parsedMemoryContent = memoryContent === null || memoryContent === ''
? undefined
: !isNaN(Number(memoryContent)) ? Number(memoryContent) : memoryContent
form.setFieldsValue({ form.setFieldsValue({
...response, ...response,
tools: allTools, tools: allTools,
memory: { memory: {
...response.memory, ...response.memory,
memory_content: response.memory?.memory_content ? Number(response.memory?.memory_content) : undefined memory_content: parsedMemoryContent
} }
}) })
setData({ setData({