-
Notifications
You must be signed in to change notification settings - Fork 614
feat: add sanitizeText utility for clipboard data handling #843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughImplements capture-phase paste handling in ChatInput.vue to sanitize text and process clipboard files before TipTap insertion. Adds a sanitizeText utility. Integrates sanitized insertion, file parsing (images and others), selection syncing, event deduplication, and cleanup of event listeners. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor U as User
participant B as Browser
participant CI as ChatInput.vue
participant E as TipTap Editor
participant S as sanitizeText
participant FS as File System
U->>B: Paste (Ctrl+V / Cmd+V)
B-->>CI: paste (capture phase)
alt Event already handled (_deepchatHandled)
CI-->>B: Ignore event
else Clipboard has files
CI->>B: preventDefault()
CI->>CI: Parse files
alt Image file
CI->>FS: Convert to base64 & write temp file
FS-->>CI: Temp path
CI->>CI: Build MessageFile + thumbnail
else Other file
CI->>CI: Resolve path & mime
CI->>CI: Build FileInfo
end
CI->>CI: Push to selectedFiles
CI-->>B: Emit file-upload (if any)
else Plain text
CI->>B: preventDefault()
CI->>S: sanitizeText(clipboardText, maxLen?)
S-->>CI: sanitizedText
CI->>E: insertContentAt(selection|cursor, sanitizedText)
CI->>CI: Sync inputText
end
note over CI,E: TipTap default paste path remains for non-captured flows
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
✨ Finishing Touches
🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 4
🧹 Nitpick comments (6)
src/renderer/src/lib/sanitizeText.ts (3)
1-1: Add explicit return type for clarity and stricter typingBe explicit on public util return types.
Apply this diff:
-export function sanitizeText(s: string | null | undefined, maxLen?: number) { +export function sanitizeText(s: string | null | undefined, maxLen?: number): string {
24-26: Truncate without splitting surrogate pairs/grapheme clustersslice(0, maxLen) can split emoji/surrogates. Use code-point or grapheme-aware truncation.
Apply this diff:
- if (typeof maxLen === 'number' && isFinite(maxLen) && maxLen >= 0 && out.length > maxLen) { - out = out.slice(0, maxLen) - } + if (typeof maxLen === 'number' && isFinite(maxLen) && maxLen >= 0 && out.length > maxLen) { + // code point–safe truncation + out = Array.from(out).slice(0, maxLen).join('') + }
6-6: Silence control-character regex lint or replace with a predicateOxLint/Biome often flag control chars in regex. Either suppress at rule-level with the tool you use, or replace with a predicate approach. Current behavior is correct; failing lint can block CI.
Option A (keep regex; suppress tooling near-line):
- // eslint-disable-next-line no-control-regex + // oxlint-disable-next-line suspicious/noControlCharactersInRegexOption B (predicate):
- out = out.replace(/[\x00-\x08\x0B\x0C\x0E-\x1F\x7F]/g, '') + out = out.replace(/[\x00-\x1F\x7F]/g, (c) => (c === '\n' || c === '\r' || c === '\t' ? c : ''))src/renderer/src/components/ChatInput.vue (3)
1103-1111: Cleanup: remove custom window and document listeners on unmountThe visibilitychange and context-menu-ask-ai listeners are never removed; add cleanup to avoid leaks.
Example patch (add handler refs and remove):
onMounted(() => { + const onAskAI = (e: any) => { + inputText.value = e.detail + editor.commands.setContent(e.detail) + editor.commands.focus() + } + const onVisibility = () => { + if (!document.hidden) { + setTimeout(() => { + restoreFocus() + }, 100) + } + } - // eslint-disable-next-line @typescript-eslint/no-explicit-any - window.addEventListener('context-menu-ask-ai', (e: any) => { - inputText.value = e.detail - editor.commands.setContent(e.detail) - editor.commands.focus() - }) + window.addEventListener('context-menu-ask-ai', onAskAI) - document.addEventListener('visibilitychange', () => { - if (!document.hidden) { - setTimeout(() => { - restoreFocus() - }, 100) - } - }) + document.addEventListener('visibilitychange', onVisibility) + ;(window as any)._deepchatListeners = { onAskAI, onVisibility } }) onUnmounted(() => { stopRateLimitPolling() window.electron.ipcRenderer.removeAllListeners(RATE_LIMIT_EVENTS.CONFIG_UPDATED) window.electron.ipcRenderer.removeAllListeners(RATE_LIMIT_EVENTS.REQUEST_EXECUTED) window.electron.ipcRenderer.removeAllListeners(RATE_LIMIT_EVENTS.REQUEST_QUEUED) // Remove capture-phase paste listener try { if (editorPasteHandler && editor && editor.view && editor.view.dom) { editor.view.dom.removeEventListener('paste', editorPasteHandler as EventListener, true) editorPasteHandler = null } } catch (err) { console.warn('Failed to remove editor paste handler', err) } + try { + const l = (window as any)._deepchatListeners + if (l) { + window.removeEventListener('context-menu-ask-ai', l.onAskAI) + document.removeEventListener('visibilitychange', l.onVisibility) + ;(window as any)._deepchatListeners = null + } + } catch (err) { + console.warn('Failed to remove global listeners', err) + } })
532-535: Logs and comments should be in English; prefer structured logsConsole messages are in Chinese and unstructured. Per guidelines, use English and structured logs (level, context). Consider a small logger wrapper.
Example:
- console.error('文件处理失败:', error) + console.error('[ERROR] paste:file-process-failed', { file: file.name, error })Also applies to: 558-559, 934-935
1068-1075: Optional: enforce a sane max paste lengthLarge pastes can freeze the editor. Consider a maxLen (e.g., 50_000 code points) and show a toast when truncating.
Example:
- const clean = sanitizeText(text) + const MAX_PASTE = 50_000 + const clean = sanitizeText(text, MAX_PASTE) + if (Array.from(text).length > MAX_PASTE) { + toast({ title: t('chat.input.pasteTruncatedTitle'), description: t('chat.input.pasteTruncatedDesc', { max: MAX_PASTE }) }) + }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
src/renderer/src/components/ChatInput.vue(4 hunks)src/renderer/src/lib/sanitizeText.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (13)
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/development-setup.mdc)
**/*.{js,jsx,ts,tsx}: 使用 OxLint 进行代码检查
Log和注释使用英文书写
Files:
src/renderer/src/lib/sanitizeText.ts
src/{main,renderer}/**/*.ts
📄 CodeRabbit inference engine (.cursor/rules/electron-best-practices.mdc)
src/{main,renderer}/**/*.ts: Use context isolation for improved security
Implement proper inter-process communication (IPC) patterns
Optimize application startup time with lazy loading
Implement proper error handling and logging for debugging
Files:
src/renderer/src/lib/sanitizeText.ts
**/*.{ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/error-logging.mdc)
**/*.{ts,tsx}: 始终使用 try-catch 处理可能的错误
提供有意义的错误信息
记录详细的错误日志
优雅降级处理
日志应包含时间戳、日志级别、错误代码、错误描述、堆栈跟踪(如适用)、相关上下文信息
日志级别应包括 ERROR、WARN、INFO、DEBUG
不要吞掉错误
提供用户友好的错误信息
实现错误重试机制
避免记录敏感信息
使用结构化日志
设置适当的日志级别Enable and adhere to strict TypeScript type checking across the codebase
Files:
src/renderer/src/lib/sanitizeText.ts
src/renderer/src/**/*
📄 CodeRabbit inference engine (.cursor/rules/i18n.mdc)
src/renderer/src/**/*: All user-facing strings must use i18n keys (avoid hardcoded user-visible text in code)
Use the 'vue-i18n' framework for all internationalization in the renderer
Ensure all user-visible text in the renderer uses the translation system
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
src/renderer/**/*.{vue,ts,js,tsx,jsx}
📄 CodeRabbit inference engine (.cursor/rules/project-structure.mdc)
渲染进程代码放在
src/renderer
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
src/renderer/src/**/*.{vue,ts,tsx,js,jsx}
📄 CodeRabbit inference engine (.cursor/rules/vue-best-practices.mdc)
src/renderer/src/**/*.{vue,ts,tsx,js,jsx}: Use the Composition API for better code organization and reusability
Implement proper state management with Pinia
Utilize Vue Router for navigation and route management
Leverage Vue's built-in reactivity system for efficient data handling
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
src/renderer/**/*.{ts,tsx,vue}
📄 CodeRabbit inference engine (.cursor/rules/vue-shadcn.mdc)
src/renderer/**/*.{ts,tsx,vue}: Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
Use TypeScript for all code; prefer types over interfaces.
Avoid enums; use const objects instead.
Use arrow functions for methods and computed properties.
Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
src/renderer/**/*.{vue,ts}
📄 CodeRabbit inference engine (.cursor/rules/vue-shadcn.mdc)
Implement lazy loading for routes and components.
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
src/renderer/**/*.{ts,vue}
📄 CodeRabbit inference engine (.cursor/rules/vue-shadcn.mdc)
src/renderer/**/*.{ts,vue}: Use useFetch and useAsyncData for data fetching.
Implement SEO best practices using Nuxt's useHead and useSeoMeta.Use Pinia for frontend state management
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
**/*.{ts,tsx,js,jsx,vue}
📄 CodeRabbit inference engine (CLAUDE.md)
Write logs and comments in English
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
src/renderer/src/**
📄 CodeRabbit inference engine (CLAUDE.md)
Place full application UI functionality (tab content) under src/renderer/src/ organized by feature
Files:
src/renderer/src/lib/sanitizeText.tssrc/renderer/src/components/ChatInput.vue
src/renderer/src/**/*.vue
📄 CodeRabbit inference engine (.cursor/rules/vue-best-practices.mdc)
Use scoped styles to prevent CSS conflicts between components
Files:
src/renderer/src/components/ChatInput.vue
src/renderer/**/*.vue
📄 CodeRabbit inference engine (CLAUDE.md)
src/renderer/**/*.vue: Use Vue 3 Composition API for all Vue components
Use Tailwind CSS with scoped styles for component styling
When creating new UI components, use Composition API with proper TypeScript typing, ensure responsive design (Tailwind), and include error/loading states
Files:
src/renderer/src/components/ChatInput.vue
🪛 Biome (2.1.2)
src/renderer/src/lib/sanitizeText.ts
[error] 6-6: Unexpected control character in a regular expression.
Control characters are unusual and potentially incorrect inputs, so they are disallowed.
(lint/suspicious/noControlCharactersInRegex)
[error] 6-6: Unexpected control character in a regular expression.
Control characters are unusual and potentially incorrect inputs, so they are disallowed.
(lint/suspicious/noControlCharactersInRegex)
[error] 6-6: Unexpected control character in a regular expression.
Control characters are unusual and potentially incorrect inputs, so they are disallowed.
(lint/suspicious/noControlCharactersInRegex)
[error] 6-6: Unexpected control character in a regular expression.
Control characters are unusual and potentially incorrect inputs, so they are disallowed.
(lint/suspicious/noControlCharactersInRegex)
[error] 6-6: Unexpected control character in a regular expression.
Control characters are unusual and potentially incorrect inputs, so they are disallowed.
(lint/suspicious/noControlCharactersInRegex)
[error] 6-6: Unexpected control character in a regular expression.
Control characters are unusual and potentially incorrect inputs, so they are disallowed.
(lint/suspicious/noControlCharactersInRegex)
[error] 9-9: A character class cannot match a joined character sequence.
A zero width joiner composes several emojis into a new one. Replace the character class with an alternation.
(lint/suspicious/noMisleadingCharacterClass)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: build-check (x64)
🔇 Additional comments (1)
src/renderer/src/components/ChatInput.vue (1)
244-244: Import looks goodUsing a dedicated utility for sanitization is the right direction.
| // Avoid double-processing when we already handled the event in the | ||
| // capture-phase editor listener. | ||
| if ((e as any)?._deepchatHandled) return | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Double-processing guard blocks file pastes from capture-phase handler
You set _deepchatHandled in the capture-phase handler then call handlePaste(e), but this guard returns early, so files aren’t processed. Allow forwarded events from the capture-phase.
Apply this diff:
- // Avoid double-processing when we already handled the event in the
- // capture-phase editor listener.
- if ((e as any)?._deepchatHandled) return
+ // Avoid double-processing unless forwarded from the capture-phase editor listener
+ if ((e as any)?._deepchatHandled && !(e as any)?._fromEditorCapture) return📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| // Avoid double-processing when we already handled the event in the | |
| // capture-phase editor listener. | |
| if ((e as any)?._deepchatHandled) return | |
| // Avoid double-processing unless forwarded from the capture-phase editor listener | |
| if ((e as any)?._deepchatHandled && !(e as any)?._fromEditorCapture) return |
🤖 Prompt for AI Agents
In src/renderer/src/components/ChatInput.vue around lines 484-487, the
early-return guard that checks (e as any)?._deepchatHandled prevents paste
events forwarded from the capture-phase handler from being processed; change the
guard to only return when the event was handled and not explicitly forwarded
(e.g. if ((e as any)?._deepchatHandled && !(e as any)?._deepchatForwarded)
return), and when the capture-phase handler intentionally forwards the event to
the bubble-phase handler set e._deepchatForwarded = true before calling
handlePaste(e) so forwarded events are allowed through.
| // Attach a capture-phase paste listener directly to the editor DOM so we | ||
| // can sanitize/handle clipboard data before TipTap inserts it. | ||
| try { | ||
| if (editor && editor.view && editor.view.dom) { | ||
| editorPasteHandler = (e: ClipboardEvent) => { | ||
| try { | ||
| // mark event to avoid double-processing | ||
| ;(e as any)._deepchatHandled = true | ||
| const files = e.clipboardData?.files | ||
| if (files && files.length > 0) { | ||
| // Prevent TipTap from treating files as plain text | ||
| e.preventDefault() | ||
| e.stopPropagation() | ||
| void handlePaste(e) | ||
| return | ||
| } | ||
| const text = e.clipboardData?.getData('text/plain') || '' | ||
| if (text) { | ||
| e.preventDefault() | ||
| e.stopPropagation() | ||
| const clean = sanitizeText(text) | ||
| const sel = editor.state.selection | ||
| const from = sel.from | ||
| const to = sel.to | ||
| // Replace current selection (or insert at cursor) with sanitized text | ||
| editor.commands.insertContentAt({ from, to }, clean, { updateSelection: true }) | ||
| // keep the reactive inputText in sync | ||
| inputText.value = editor.getText() | ||
| } | ||
| } catch (err) { | ||
| console.error('editor paste handler error', err) | ||
| } | ||
| } | ||
| editor.view.dom.addEventListener('paste', editorPasteHandler as EventListener, true) | ||
| } | ||
| } catch (err) { | ||
| console.warn('Failed to attach editor paste handler', err) | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Capture-phase paste handler: mark forwarding and use insertText to avoid HTML parsing
- Mark events with _fromEditorCapture so handlePaste can run for files.
- Use insertText over insertContentAt(string) to avoid interpreting HTML and to respect the current selection.
Apply this diff:
editorPasteHandler = (e: ClipboardEvent) => {
try {
// mark event to avoid double-processing
- ;(e as any)._deepchatHandled = true
+ ;(e as any)._deepchatHandled = true
+ ;(e as any)._fromEditorCapture = true
const files = e.clipboardData?.files
if (files && files.length > 0) {
// Prevent TipTap from treating files as plain text
e.preventDefault()
e.stopPropagation()
- void handlePaste(e)
+ void handlePaste(e)
return
}
const text = e.clipboardData?.getData('text/plain') || ''
if (text) {
e.preventDefault()
e.stopPropagation()
const clean = sanitizeText(text)
- const sel = editor.state.selection
- const from = sel.from
- const to = sel.to
-
- // Replace current selection (or insert at cursor) with sanitized text
- editor.commands.insertContentAt({ from, to }, clean, { updateSelection: true })
- // keep the reactive inputText in sync
- inputText.value = editor.getText()
+ const { from, to } = editor.state.selection
+ editor
+ .chain()
+ .setTextSelection({ from, to })
+ .insertText(clean)
+ .run()
+ inputText.value = editor.getText()
}
} catch (err) {
console.error('editor paste handler error', err)
}
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| // Attach a capture-phase paste listener directly to the editor DOM so we | |
| // can sanitize/handle clipboard data before TipTap inserts it. | |
| try { | |
| if (editor && editor.view && editor.view.dom) { | |
| editorPasteHandler = (e: ClipboardEvent) => { | |
| try { | |
| // mark event to avoid double-processing | |
| ;(e as any)._deepchatHandled = true | |
| const files = e.clipboardData?.files | |
| if (files && files.length > 0) { | |
| // Prevent TipTap from treating files as plain text | |
| e.preventDefault() | |
| e.stopPropagation() | |
| void handlePaste(e) | |
| return | |
| } | |
| const text = e.clipboardData?.getData('text/plain') || '' | |
| if (text) { | |
| e.preventDefault() | |
| e.stopPropagation() | |
| const clean = sanitizeText(text) | |
| const sel = editor.state.selection | |
| const from = sel.from | |
| const to = sel.to | |
| // Replace current selection (or insert at cursor) with sanitized text | |
| editor.commands.insertContentAt({ from, to }, clean, { updateSelection: true }) | |
| // keep the reactive inputText in sync | |
| inputText.value = editor.getText() | |
| } | |
| } catch (err) { | |
| console.error('editor paste handler error', err) | |
| } | |
| } | |
| editor.view.dom.addEventListener('paste', editorPasteHandler as EventListener, true) | |
| } | |
| } catch (err) { | |
| console.warn('Failed to attach editor paste handler', err) | |
| } | |
| // Attach a capture-phase paste listener directly to the editor DOM so we | |
| // can sanitize/handle clipboard data before TipTap inserts it. | |
| try { | |
| if (editor && editor.view && editor.view.dom) { | |
| editorPasteHandler = (e: ClipboardEvent) => { | |
| try { | |
| // mark event to avoid double-processing | |
| ;(e as any)._deepchatHandled = true | |
| ;(e as any)._fromEditorCapture = true | |
| const files = e.clipboardData?.files | |
| if (files && files.length > 0) { | |
| // Prevent TipTap from treating files as plain text | |
| e.preventDefault() | |
| e.stopPropagation() | |
| void handlePaste(e) | |
| return | |
| } | |
| const text = e.clipboardData?.getData('text/plain') || '' | |
| if (text) { | |
| e.preventDefault() | |
| e.stopPropagation() | |
| const clean = sanitizeText(text) | |
| const { from, to } = editor.state.selection | |
| editor | |
| .chain() | |
| .setTextSelection({ from, to }) | |
| .insertText(clean) | |
| .run() | |
| inputText.value = editor.getText() | |
| } | |
| } catch (err) { | |
| console.error('editor paste handler error', err) | |
| } | |
| } | |
| editor.view.dom.addEventListener('paste', editorPasteHandler as EventListener, true) | |
| } | |
| } catch (err) { | |
| console.warn('Failed to attach editor paste handler', err) | |
| } |
🤖 Prompt for AI Agents
In src/renderer/src/components/ChatInput.vue around lines 1050 to 1094, the
capture-phase paste handler should mark events so downstream logic knows they
originated from the editor and should use insertText rather than
insertContentAt(string) to avoid HTML parsing; update the handler to set a flag
like (e as any)._fromEditorCapture before any processing, when files exist call
handlePaste explicitly (so handlePaste can run for files) and return, and when
inserting plain text use editor.commands.insertText(clean, { from, to, select:
false }) (or the TipTap insertText equivalent) then sync inputText.value =
editor.getText(); keep the existing try/catch and
event.preventDefault()/stopPropagation() behavior and attach the handler in
capture phase.
| // Remove explicit zero-width / soft-hyphen characters | ||
| // eslint-disable-next-line no-control-regex | ||
| out = out.replace(/[\u00AD\u200B\u200C\u200D\u2060\uFEFF]/g, '') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Avoid removing ZWJ/ZWNJ; this breaks emoji and shaping for many scripts
Stripping U+200D (ZWJ) and U+200C (ZWNJ) corrupts joined emoji (family/skin-tone) and languages like Persian/Indic. Keep them by default.
Apply this diff:
- // Remove explicit zero-width / soft-hyphen characters
- // eslint-disable-next-line no-control-regex
- out = out.replace(/[\u00AD\u200B\u200C\u200D\u2060\uFEFF]/g, '')
+ // Remove explicit zero-width spaces, soft hyphen, BOM (keep ZWJ/ZWNJ to avoid breaking text shaping/emoji)
+ // biome-ignore lint/suspicious/noMisleadingCharacterClass: using alternation for clarity
+ out = out.replace(/(?:\u00AD|\u200B|\u2060|\uFEFF)/g, '')📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| // Remove explicit zero-width / soft-hyphen characters | |
| // eslint-disable-next-line no-control-regex | |
| out = out.replace(/[\u00AD\u200B\u200C\u200D\u2060\uFEFF]/g, '') | |
| // Remove explicit zero-width spaces, soft hyphen, BOM (keep ZWJ/ZWNJ to avoid breaking text shaping/emoji) | |
| // biome-ignore lint/suspicious/noMisleadingCharacterClass: using alternation for clarity | |
| out = out.replace(/(?:\u00AD|\u200B|\u2060|\uFEFF)/g, '') |
🧰 Tools
🪛 Biome (2.1.2)
[error] 9-9: A character class cannot match a joined character sequence.
A zero width joiner composes several emojis into a new one. Replace the character class with an alternation.
(lint/suspicious/noMisleadingCharacterClass)
🤖 Prompt for AI Agents
In src/renderer/src/lib/sanitizeText.ts around lines 7 to 9, the current regex
removes U+200C (ZWNJ) and U+200D (ZWJ) which breaks joined emoji and shaping in
many scripts; update the replacement so it does not strip ZWJ (U+200D) or ZWNJ
(U+200C) — remove those two codepoints from the character class, keep removing
other zero-width characters (e.g., U+00AD U+200B U+2060 U+FEFF), and update the
inline comment to note that ZWJ/ZWNJ are preserved to avoid breaking emoji and
script shaping.
| // Normalize and strip combining marks; use Unicode property escapes when available | ||
| try { | ||
| out = out.normalize('NFD').replace(/\p{M}/gu, '').normalize('NFC') | ||
| } catch { | ||
| out = out.normalize | ||
| ? out | ||
| .normalize('NFD') | ||
| .replace(/[\u0300-\u036f]/g, '') | ||
| .normalize('NFC') | ||
| : out | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Don’t strip all combining marks by default; this harms i18n
Removing all diacritics converts José → Jose, München → Munchen, etc. For a chat input, that’s data loss. Normalize to NFC only; if mark-stripping is needed, make it opt-in via a flag.
Apply this diff:
- // Normalize and strip combining marks; use Unicode property escapes when available
- try {
- out = out.normalize('NFD').replace(/\p{M}/gu, '').normalize('NFC')
- } catch {
- out = out.normalize
- ? out
- .normalize('NFD')
- .replace(/[\u0300-\u036f]/g, '')
- .normalize('NFC')
- : out
- }
+ // Normalize to NFC for canonical consistency; avoid stripping marks by default
+ try {
+ out = out.normalize('NFC')
+ } catch {
+ // ignore if not supported
+ }📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| // Normalize and strip combining marks; use Unicode property escapes when available | |
| try { | |
| out = out.normalize('NFD').replace(/\p{M}/gu, '').normalize('NFC') | |
| } catch { | |
| out = out.normalize | |
| ? out | |
| .normalize('NFD') | |
| .replace(/[\u0300-\u036f]/g, '') | |
| .normalize('NFC') | |
| : out | |
| } | |
| // Normalize to NFC for canonical consistency; avoid stripping marks by default | |
| try { | |
| out = out.normalize('NFC') | |
| } catch { | |
| // ignore if not supported | |
| } |
* fix: chat confg need sync to new value when change model in chat (#823) * fix: gemini nano banana not read image from chatinput * fix: remove file-type ,this will mark html as audio (#824) * fix: Solve the problem of the window becoming larger when dragging floating button under Windows (#826) * fix: improve OpenAI compatible provider compatibility with third-party services * chore: update vue-renderer-markdown to v0.0.35 (#827) * refactor: remove custom-prompts-server and decouple prompts from MCP lifecycle (#829) - Remove custom-prompts-server service entirely including configuration - Implement data source merging in MCP store to load prompts from both config and MCP - Add upgrade migration logic for versions < 0.3.5 to clean up old configurations - Ensure @ operations work independently of MCP state through config data source - Update CLAUDE.md with prompt management guidelines The @ prompt functionality now works completely independently of MCP, loading custom prompts directly from config storage while maintaining full compatibility with existing MCP prompt sources. * chore: add better log for mcp tool name * feat: ux update (#831) * feat: ux update * chore: format * feat: setting provider ux update (#832) * feat: add current datetime to system prompt - Add current date and time information to user's system prompt when not empty - Include complete datetime with timezone, year, month, day, hour, minute, second - Apply to both preparePromptContent and buildContinueToolCallContext methods - Update token calculation to use processed system prompt for accuracy - Skip datetime addition for image generation models and empty prompts * refactor: extract system prompt datetime enhancement to common method - Add enhanceSystemPromptWithDateTime private method to reduce code duplication - Update both preparePromptContent and buildContinueToolCallContext to use common method - Improve code maintainability and ensure consistency across all system prompt processing - Add comprehensive JSDoc documentation for the new method * fix(markdown): auto-wrap hide scroll (#833) * feat: add enable_thinking parameter support for siliconcloud (#835) * chore: bump deps (#834) * chore: bump up deps * fix: change win arm to wasm32 sharp * chore: revert sharp config * feat: drop windows arm support * fix(coderabbitai): remove action for windows arm64 * refactor: adjust scroll-to-bottom button glow effect (#837) * feat: add mutual exclusive confirmation dialogs for DeepSeek-V3.1 (#838) * feat: add sanitizeText utility for clipboard data handling (#843) * feat: support canary upgrade (#840) * feat: support canary upgrade * feat: add update channel selection for stable/canary versions - Add update channel configuration to config presenter - Implement dynamic URL switching for version checks and downloads - Add UI selector in AboutUsSettings for channel selection - Support stable and canary update channels with different endpoints - Add internationalization support for channel selection * chore: change contributors charts to openomy * refactor: improve update channel handling and network resilience - Sanitize update channel input to prevent invalid values - Add 10-second timeout to version check requests to prevent hanging - Treat unknown channels as 'upgrade' (stable) for robustness - Improve error handling for network timeouts and invalid channels * feat: implement thinking parameter support for doubao models (#842) * feat: implement dedicated DashScope provider with enable_thinking support (#844) * feat: implement dedicated DashScope provider with enable_thinking support * refactor: remove unnecessary API key status check methods from DashscopeProvider * fix: prioritize provider.id over apiType in createProviderInstance (#846) * feat: add qwen3 thinking budget support (#848) * feat: add qwen3 thinking budget support * fix: add missing gemini.onlySupported key in zh-CN locale * refactor: merge duplicate silicon case statements in provider creation * feat: add qwen3 thinking budget support in ChatConfig (#849) * refactor(types): 🚀split monolithic presenter.d.ts into strict per-domain *.presenter.d.ts + typed core layer (#847) * docs: Add strong-typed message architecture and implementation guidelines - Update message-architecture.md with strong-typed design, remove compatibility compromises - Add event-to-UI mapping table and rendering checklist for contract compliance - Create presenter-split-plan.md for type system refactoring - Add implementation-tasks.md with phased rollout plan - Create .cursor/rules/provider-guidelines.mdc for provider implementation guidance This establishes a foundation for strong-typed, maintainable message architecture without legacy compatibility debt. * types(core): add strong-typed core types and barrel exports\n\n- Add usage.ts (UsageStats, RateLimitInfo)\n- Add llm-events.ts (discriminated union + factories + guards)\n- Add agent-events.ts (LLMAgentEvent*, shared types)\n- Add chat.ts (Message/AssistantMessageBlock/UserMessageContent)\n- Add mcp.ts (MCP content/response/definition)\n- Add types/index.d.ts barrel exports\n\nNo compatibility shims included by design. * refactor(types): move legacy presenters and add @shared/presenter stub; keep legacy exports in types/index to maintain build\n\n- Move legacy presenters to src/shared/types/presenters/legacy.presenters.d.ts\n- Add src/shared/presenter.d.ts re-export stub\n- Temporarily export only legacy presenters from types/index.d.ts to avoid type mismatches\n- Update implementation-tasks.md (Stage 2 done)\n\nNext: progressive import updates to new cores, then flip barrel to new types and delete legacy. * refactor(types): alias legacy core message types to strong-typed core (B-plan)\n\n- legacy.presenters.d.ts now re-exports ChatMessage/ChatMessageContent/LLMAgentEvent/LLMAgentEventData/LLMCoreStreamEvent from core\n- Prepares for flipping interfaces without changing import sites * docs(tasks): mark Phase 3 as completed\n\n- Successfully implemented B-plan approach with type aliasing\n- Unified core message types (ChatMessage, LLMAgentEvent, LLMCoreStreamEvent)\n- Created core model types and maintained build compatibility\n- All type checks passing with no breaking changes * fix(types): revert to legacy-only exports and fix MESSAGE_ROLE\n\n- Revert types/index.d.ts to only export legacy presenters\n- Remove 'function' from MESSAGE_ROLE to match core definition\n- Maintain build stability while preserving type unification work * feat(provider): implement factory functions for LLMCoreStreamEvent\n\n- Replace all manual event creation with createStreamEvent factory functions\n- Ensures type safety and consistent event structure\n- Updated OpenAICompatibleProvider with strong-typed events:\n - text, reasoning, toolCallStart, toolCallChunk, toolCallEnd\n - error, usage, stop, imageData events\n- All type checks passing\n- Phase 4.1 completed: Provider now outputs LLMCoreStreamEvent with factory construction * feat(provider): update OllamaProvider with factory functions\n\n- Replace all manual event creation with createStreamEvent factory functions\n- Ensures consistent tool_call_start → tool_call_chunk → tool_call_end sequence\n- Updated all event types: text, reasoning, toolCall*, usage, stop, error\n- Maintains proper tool call ID aggregation and sequencing\n- Phase 4.2 completed: Tool call sequences now strictly follow start/chunk/end pattern * docs(tasks): update Phase 4 progress\n\n- Completed Provider strong-typed event output with factory functions\n- Completed tool_call_* strict start/chunk/end sequences\n- Completed usage event sent before stop in all providers\n- Updated implementation tasks document with current progress * feat(phase4): complete Provider strong-typed event integration\n\n- Added factory functions import to AwsBedrockProvider\n- Updated error handling to use createStreamEvent.error() + createStreamEvent.stop('error')\n- Created comprehensive unit tests for LLMCoreStreamEvent factory functions\n- Tests validate: event creation, tool call sequences, error+stop patterns, type guards\n- All 12 core event tests passing ✅\n\n## Phase 4 Completed:\n- ✅ Provider strong-typed event output (factory construction)\n- ✅ tool_call_* strict start/chunk/end sequences with ID aggregation\n- ✅ Usage events sent before stop in all providers\n- ✅ Rate limit events (handled at Presenter layer)\n- ✅ Unified error + stop event patterns\n- ✅ Comprehensive unit tests for sequences/fields/boundaries * feat(phase5): complete Agent & UI alignment ## Phase 5 Completed: Agent & UI Alignment ✅ ### 1. Agent Layer Enhancement - ✅ Agent consumes only CoreEvent and outputs LLMAgentEvent - ✅ Strict separation of response/error/end event types - ✅ Added rate_limit event handling in Agent layer - ✅ Maintained proper event transformation pipeline ### 2. UI Layer Unification - ✅ Removed standalone tool_call_permission type - ✅ Unified to action + action_type pattern - ✅ Updated all UI components and thread presenter logic - ✅ Preserved backward compatibility with conditional rendering ### 3. Renderer Mapping & Testing - ✅ Created comprehensive renderer contract tests (17 tests) - ✅ Added message block data structure snapshot tests (14 tests) - ✅ Validated event-to-UI block mapping compliance - ✅ Ensured consistent status transitions and type safety ### Key Technical Achievements: - **Type Safety**: All event transformations now type-safe - **Consistency**: Unified action_type handling across codebase - **Testing**: 31 new tests covering contracts and snapshots - **Architecture**: Clean separation between Agent/UI concerns - **Quality**: All lint, format, and type checks passing ✅ ### Files Modified: - Agent layer: llmProviderPresenter/index.ts - UI components: MessageItemAssistant.vue - Thread logic: threadPresenter/index.ts - Type definitions: shared/chat.d.ts - Tests: rendererContract.test.ts, messageBlockSnapshot.test.ts Ready for Phase 6: Quality & Tools 🚀 * feat(phase6): complete Quality & Tools phase ## Phase 6 Completed: Quality & Tools ✅ ### 1. Table-Driven Contract Tests - ✅ Created comprehensive event mapping contract tests (25 test cases) - ✅ Validated all event types from architecture mapping table - ✅ Verified status transitions and type constraints - ✅ Added tool call ID aggregation and lifecycle validation - ✅ Implemented error recovery pattern testing ### 2. Performance Evaluation & Stress Testing - ✅ Large text content processing (50KB < 10ms) - ✅ Large reasoning content handling (100KB < 15ms) - ✅ Large image data processing (1MB < 20ms) - ✅ Batch image processing (100 images < 50ms) - ✅ High-frequency event processing (1000 events < 100ms) - ✅ Mixed event type handling (500 events < 80ms) - ✅ Memory leak prevention (5000 events < 500ms) - ✅ Extreme parameter handling (10KB params < 5ms) - ✅ Concurrent processing simulation (10 workers < 100ms) ### Key Technical Achievements: - **Comprehensive Testing**: 67 tests passing across all scenarios - **Performance Validation**: All benchmarks meet performance targets - **Type Safety**: Full TypeScript compliance (0 errors) - **Code Quality**: Lint and format checks passing ✅ - **Architecture Compliance**: All mapping table rules verified - **Stress Testing**: System handles extreme loads efficiently ### Test Coverage Summary: - Event mapping contract tests: 25 tests ✅ - Renderer contract tests: 17 tests ✅ - Performance evaluation tests: 9 tests ✅ - Core event factory tests: 12 tests ✅ - Message block snapshot tests: 14 tests ✅ - Shell integration tests: 8 tests ✅ ### Files Added: - test/renderer/message/eventMappingTable.test.ts (comprehensive mapping validation) - test/renderer/message/performanceEvaluation.test.ts (stress & performance testing) Ready for production deployment with full quality assurance! 🚀 * fix(providers): complete strong-typed event integration across all providers * fix(vitest): modify test case * fix: default settings * chore: update doc * fix(ci): remove duplicate check in pr ci * feat: add pnpm cache for pr check * fix(ci): pr check with pnpm cache * fix(ci): change cache key to package.json * ci: remove pnpm cache * feat: add glow breathing effect to scroll-to-bottom button (#850) * feat: add glow breathing effect to scroll-to-bottom button * fix: ensure exclusive display between MessageList and ArtifactDialog * fix: refine MessageList–ArtifactDialog interaction logic; correct z-order between dialog and ArtifactDialog * chore: prettier .vue * feat: add web search support with configurable options for dashscope (#851) * feat: add web search support with configurable options for dashscope * fix: correct qwen model parameters to match official documentation * feat: add web search support with configurable options for dashscope (#852) * feat: add web search support with configurable options for dashscope * fix: correct qwen model parameters to match official documentation * feat: add search configuration support to ChatConfig components * fix: fix enableSearch state sync and parameter passing issues * fix: preserve search settings during data import * feat: add dashscope commercial models to enable_thinking support (#853) * feat: add search capability icon for model list (#854) * feat: add search capability icon for model list * fix: clear search settings when creating new conversation * feat(markdown): Thinking panel now supports LaTeX compilation for mathematical formulas & markdown performance optimization (#857) * feat(markdown): 思考栏支持数学公式latex编译显示 & markdown 性能优化 close: #845 * chore: lint * chore(ai): update claude code rules and agents * fix(ui): revert Dialog z-index to z-50 to fix dropdown visibility Reverts DialogContent z-index from z-[100] back to z-50 to resolve issue where Select and EmojiPicker dropdowns were not appearing. This maintains proper layering hierarchy without breaking other UI components. * feat: upgrade vue-renderer-markdown & vue-use-monaco (#862) 1. ignore math-block warning 2. Compatible with the syntax issues of mermaid produced by AI, greatly reducing the probability of mermaid rendering errors * feat(dashscope): add qwen3-max-preview model (#865) * fix: mcp params support more types (#861) * feat(mcp): enhance tool parameter display with enum type support - Add enum parameter type detection and enhanced display - Show enum parameters with distinct blue badge styling (enum(string), array[enum(string)]) - Display allowed values for both direct enum and array item enum parameters - Add i18n support for "allowedValues" and "arrayItemValues" labels - Maintain consistent UI design with existing parameter display patterns - Improve developer experience when debugging MCP tools with constrained parameters * fix: enum params support * fix(context-menu): handle local file paths in image save functionality - Fix URL parsing error when saving images from local file paths - Add proper handling for http/https URLs, file:// URLs, and direct file paths - Use fs.promises for reading local files instead of net.fetch for invalid URLs - Prevent "Failed to parse URL from" error when saving local images * fix(context-menu): improve URL handling robustness in image save - Add try-catch around net.fetch to handle invalid URLs gracefully - Implement fallback methods for file:// URLs and local file paths - Add debug logging to track source URL values for troubleshooting - Prevent "Failed to parse URL from" errors with comprehensive URL validation * fix(context-menu): handle empty srcURL in image save functionality - Add comprehensive URL detection when srcURL is empty - Implement fallback URL sources (linkURL, pageURL) for better compatibility - Add debug logging to track all available context menu parameters - Prevent "Failed to parse URL from" errors caused by empty URLs - Provide clear error message when no valid URL can be found * chore: format code * fix: ai review * fix: prevent @ symbol remaining when deleting mentions (#867) * Merge commit from fork * feat: implement separated system and custom prompt management (#868) * feat: implement separated system and custom prompt management * style: code fmt * fix: add migration for legacy default_system_prompt to system_prompts * feat: add Moonshot model configurations (#869) * refactor: translate all cn comments and log to en (#871) * refactor: translate all cn comments and log to en * fix: revert translate in params * feat: add reasoning support for Grok thinking models (#873) * feat: add reasoning support for Grok thinking models * fix: code lint * fix: escaping character issue --------- Co-authored-by: zerob13 <zerob13@gmail.com> --------- Co-authored-by: hllshiro <40970081+hllshiro@users.noreply.github.com> Co-authored-by: yyhhyyyyyy <yyhhyyyyyy8@gmail.com> Co-authored-by: xiaomo <wegi866@gmail.com> Co-authored-by: Simon He <57086651+Simon-He95@users.noreply.github.com> Co-authored-by: luy <12696648@qq.com>
Pull Request Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
*For example: I'm always frustrated when [...] *
Describe the solution you'd like
A clear and concise description of what you want to happen.
UI/UX changes for Desktop Application
If this PR introduces UI/UX changes, please describe them in detail.
Platform Compatibility Notes
If this PR has specific platform compatibility considerations (Windows, macOS, Linux), please describe them here.
Additional context
Add any other context about the pull request here.
Pull Request Description (中文)
你的功能请求是否与某个问题有关?请描述一下。
请对问题进行清晰扼要的描述。
*例如:我增加了 [...] 的功能 *
请描述你希望的解决方案
请对你希望实现的效果进行清晰扼要的描述。
桌面应用程序的 UI/UX 更改
如果此 PR 引入了 UI/UX 更改,请详细描述它们。
平台兼容性注意事项
如果此 PR 具有特定的平台兼容性考虑因素(Windows、macOS、Linux),请在此处描述。
附加背景
在此处添加关于此 Pull Request 的任何其他背景信息。
Summary by CodeRabbit
New Features
Improvements
Bug Fixes