fix: handle empty reasoning_content from non-standard APIs

gene9831 · gene9831 · commit 8fe48f6e56f1 · 2026-04-23T11:42:09.000+08:00
Some non-standard APIs may return an empty string for
`reasoning_content` even when the model does not support
deep reasoning. This change improves compatibility by
tolerating that response shape.
diff --git a/packages/components/src/bubble/renderers/defaultRenderers.ts b/packages/components/src/bubble/renderers/defaultRenderers.ts
@@ -25,7 +25,7 @@ export const defaultContentRendererMatches: Array<BubbleContentRendererMatch> =
     priority: BubbleRendererMatchPriority.LOADING,
   },
   {
-    find: (message) => typeof message.reasoning_content === 'string',
+    find: (message) => typeof message.reasoning_content === 'string' && message.reasoning_content.trim() !== '',
     renderer: markRaw(Reasoning),
     priority: BubbleRendererMatchPriority.NORMAL,
   },

Original file line number	Diff line number	Diff line change
`@@ -25,7 +25,7 @@ export const defaultContentRendererMatches: Array<BubbleContentRendererMatch> =`
`25`	`25`	`priority: BubbleRendererMatchPriority.LOADING,`
`26`	`26`	`},`
`27`	`27`	`{`
`28`		`- find: (message) => typeof message.reasoning_content === 'string',`
	`28`	`+ find: (message) => typeof message.reasoning_content === 'string' && message.reasoning_content.trim() !== '',`
`29`	`29`	`renderer: markRaw(Reasoning),`
`30`	`30`	`priority: BubbleRendererMatchPriority.NORMAL,`
`31`	`31`	`},`