feature: renderer dialog for main process #629

hllshiro · 2025-07-22T12:10:39Z

Pull Request Description (中文)

你的功能请求是否与某个问题有关？请描述一下。
请对问题进行清晰扼要的描述。
增加dialog弹窗功能，用以替代electron dialog

桌面应用程序的 UI/UX 更改
如果此 PR 引入了 UI/UX 更改，请详细描述它们。

如果适用，请包含屏幕截图或 GIF 以直观地演示更改。
解释 UI/UX 决策背后的原因，以及它们如何改善桌面应用程序的用户体验。

平台兼容性注意事项
如果此 PR 具有特定的平台兼容性考虑因素（Windows、macOS、Linux），请在此处描述。

是否有任何平台特定的行为或代码调整？无
你是否已在所有相关平台上进行过测试？无

附加背景
颜色可能要再改改，或者接口支持自定义

Summary by CodeRabbit

New Features
- Introduced a global message dialog for displaying customizable alerts and confirmations.
- Added support for dialogs with multiple buttons, default button selection, timeouts, and internationalization.
- Dialogs now appear on the active tab and can automatically switch to the foreground if needed.
- Added dialog communication events between main and renderer processes to handle dialog requests and responses.
Improvements
- Enhanced user experience with dynamic dialog content, icons based on dialog type, and countdown timers for actions.
- Implemented automatic dialog timeout handling with default button selection.
- Improved dialog state management and error handling to prevent stuck dialogs.

…onent

…ew closeable option

…ment with enhanced type definitions

…ageDialog component

…ons and improve dialog timeout handling

coderabbitai · 2025-07-22T12:10:46Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This change introduces a cross-process dialog system between the main and renderer processes. It includes new event constants for dialog requests and responses, a DialogPresenter class to manage dialog state and communication, updates to the presenter interfaces, a Vue component for displaying dialogs, a Pinia store for dialog state management, and integration of the dialog UI into the main application.

Changes

File(s)	Change Summary
src/main/events.ts, src/renderer/src/events.ts	Added `DIALOG_EVENTS` constant with `REQUEST` and `RESPONSE` event string constants for dialog communication.
src/main/presenter/dialogPresenter/index.ts	Added `DialogPresenter` class implementing `IDialogPresenter` for managing dialog requests and responses.
src/main/presenter/index.ts	Integrated `DialogPresenter` into the main `Presenter` class and instantiated it in the constructor.
src/renderer/src/App.vue	Imported and included the `MessageDialog` component as a global UI element.
src/renderer/src/components/ui/MessageDialog.vue	Added new `MessageDialog` Vue component for rendering customizable dialogs with dynamic buttons and timeouts.
src/renderer/src/stores/dialog.ts	Added Pinia store `useDialogStore` to manage dialog state, handle requests, and implement countdown logic.
src/shared/presenter.d.ts	Extended `IPresenter`, added dialog-related types and `IDialogPresenter` interface for dialog contract.

Sequence Diagram(s)

sequenceDiagram
    participant MainProcess
    participant DialogPresenter
    participant RendererProcess
    participant DialogStore
    participant MessageDialog

    MainProcess->>DialogPresenter: showDialog(request)
    DialogPresenter->>RendererProcess: DIALOG_EVENTS.REQUEST (dialog request)
    RendererProcess->>DialogStore: Receive dialog request event
    DialogStore->>MessageDialog: Update dialog state (show dialog)
    MessageDialog->>DialogStore: User selects button or timeout
    DialogStore->>RendererProcess: handleResponse(selected button)
    RendererProcess->>DialogPresenter: DIALOG_EVENTS.RESPONSE (dialog response)
    DialogPresenter->>MainProcess: Resolve showDialog promise with user response

Estimated code review effort

3 (~45 minutes)

Poem

In the warren of code, a dialog appears,
With buttons and timers, it calms all our fears.
From main to renderer, messages fly—
A rabbit clicks “OK” with a gleam in its eye.
Now with a hop, our UI’s more bright,
Dialogs handled left and right!
🐇💬✨

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.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 7

🧹 Nitpick comments (17)

src/renderer/src/components/ui/MessageDialog.vue (2)
69-70: Use English for comments as per coding guidelines.

The comment should be in English to follow the project's coding standards.
-/**
- * 将时间转换为合适的单位，最小为1秒，最大单位为周
- * @param ms milliseconds
- */
+/**
+ * Convert time to appropriate units, minimum 1 second, maximum unit is weeks
+ * @param ms milliseconds
+ */
87-87: Remove debug console.log statement.

Debug logging should be removed from production code or replaced with proper logging infrastructure.
-  console.log('[Dialog] getIconProps called with type:', type)
src/main/presenter/dialogPresenter/index.ts (7)
1-6: Use English for comments as per coding guidelines.

All comments should be in English to follow the project's coding standards.
 /**
- * 通过渲染进程实现的消息弹窗
- * 弹窗显示在当前活动的标签页上，如果标签页在后台，会自动切换到前台
- * 单个活动窗口内只能有一个消息弹窗，重复调用会将之前的弹窗以null触发回调
+ * Message dialog implementation via renderer process
+ * Dialog shows on the current active tab, automatically switches to foreground if tab is in background
+ * Only one message dialog per active window, repeated calls will trigger previous dialog callback with null
  * @see {@link SendTarget.DEFAULT_TAB}
  */
20-20: Remove unnecessary empty constructor.

The empty constructor is unnecessary and flagged by static analysis tools.
-  constructor() {}
22-25: Use English for method comments.

Method documentation should be in English to follow coding guidelines.
   /**
-   * 显示Dialog - 通过渲染进程实现
-   * @param request Dialog请求参数
-   * @returns Promise<DialogResponse> Dialog结果
+   * Show Dialog - implemented via renderer process
+   * @param request Dialog request parameters
+   * @returns Promise<DialogResponse> Dialog result
    */
31-31: Use English for inline comments.

Inline comments should be in English.
-          id: nanoid(8), // 最好是使用当前DEFAULT_TAB的id，便于控制单窗口内最多一个弹窗，但目前似乎缺少获取途径
+          id: nanoid(8), // Better to use current DEFAULT_TAB id to control max one dialog per window, but currently lacks access method
52-55: Use English for method comments.

Method documentation should be in English.
   /**
-   * 处理对话框响应
-   * @param response 对话框响应
+   * Handle dialog response
+   * @param response Dialog response
    */
58-58: Replace console.log with proper logging.

Use proper logging infrastructure instead of console.log.
-      console.log('[Dialog]  response received:', response)
+      // Use proper logging infrastructure here
44-44: Use English for inline comments.

Inline comments should be in English.
-        // 向渲染进程发送dialog请求
+        // Send dialog request to renderer process
src/renderer/src/stores/dialog.ts (8)
14-14: Use English for comments as per coding guidelines.

Comments should be in English to follow project standards.
-  // 清理定时器
+  // Clear timer
22-22: Use English for comments as per coding guidelines.

Comments should be in English.
-  // 启动倒计时
+  // Start countdown
36-36: Use English for comments as per coding guidelines.

Comments should be in English.
-  // 监听对话框请求事件
+  // Listen for dialog request events
56-56: Use English for comments as per coding guidelines.

Comments should be in English.
-  // 响应对话框
+  // Respond to dialog
26-34: Optimize timer interval and add error handling.

The 100ms interval is quite frequent and could impact performance. Also add error handling for the countdown logic.
     timer = setInterval(() => {
-      if (timeoutMilliseconds.value > 0) {
-        timeoutMilliseconds.value -= 100
-      } else {
-        clearTimer()
-        handleResponse(defaultButton)
+      try {
+        if (timeoutMilliseconds.value > 0) {
+          timeoutMilliseconds.value -= 1000 // Update every second instead of 100ms
+        } else {
+          clearTimer()
+          handleResponse(defaultButton)
+        }
+      } catch (error) {
+        console.error('[DialogStore] Error in countdown timer:', error)
+        clearTimer()
       }
-    }, 100)
+    }, 1000) // Update every second instead of 100ms
40-42: Use English for comments as per coding guidelines.

Inline comments should be in English.
       if(dialogRequest.value) {
-        // 如果已有对话框请求，清理之前的定时器
+        // If dialog request already exists, clear previous timer
         clearTimer()
50-50: Replace console.warn with proper logging.

Use proper logging infrastructure instead of console.warn.
-        console.warn('default params is missing or invalid:', event)
+        // Use proper logging infrastructure here
+        // console.warn('default params is missing or invalid:', event)
71-71: Consider alternative to onMounted in Pinia store.

Using onMounted in a Pinia store is unusual. Consider setting up the event listener when the store is first used or provide a proper initialization method.

The current pattern works but consider these alternatives:
-  onMounted(setupUpdateListener)
+  // Option 1: Setup immediately when store is created
+  setupUpdateListener()
+  
+  // Option 2: Provide explicit initialization
+  const initialize = () => {
+    setupUpdateListener()
+  }
Then call initialize() from the component that uses the store.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e22ad5c and 1847ffc.

📒 Files selected for processing (8)

src/main/events.ts (1 hunks)
src/main/presenter/dialogPresenter/index.ts (1 hunks)
src/main/presenter/index.ts (3 hunks)
src/renderer/src/App.vue (2 hunks)
src/renderer/src/components/ui/MessageDialog.vue (1 hunks)
src/renderer/src/events.ts (1 hunks)
src/renderer/src/stores/dialog.ts (1 hunks)
src/shared/presenter.d.ts (2 hunks)

📓 Path-based instructions (17)

**/*.{ts,tsx,js,jsx,vue}

📄 CodeRabbit Inference Engine (CLAUDE.md)

Use English for logs and comments

Files:

src/renderer/src/App.vue
src/renderer/src/events.ts
src/main/events.ts
src/main/presenter/index.ts
src/main/presenter/dialogPresenter/index.ts
src/shared/presenter.d.ts
src/renderer/src/components/ui/MessageDialog.vue
src/renderer/src/stores/dialog.ts

src/renderer/src/**/*.vue

📄 CodeRabbit Inference Engine (CLAUDE.md)

src/renderer/src/**/*.vue: Use Composition API for all Vue 3 components
Use Tailwind CSS with scoped styles for styling
Organize components by feature in src/renderer/src/
Follow existing component patterns in src/renderer/src/ when creating new UI components
Use Composition API with proper TypeScript typing for new UI components
Implement responsive design with Tailwind CSS for new UI components
Add proper error handling and loading states for new UI components

Use scoped styles to prevent CSS conflicts between components

Files:

src/renderer/src/App.vue
src/renderer/src/components/ui/MessageDialog.vue

src/renderer/src/**/*.{ts,tsx,vue}

📄 CodeRabbit Inference Engine (CLAUDE.md)

src/renderer/src/**/*.{ts,tsx,vue}: Use Pinia for frontend state management
Renderer to Main: Use usePresenter.ts composable for direct presenter method calls

Files:

src/renderer/src/App.vue
src/renderer/src/events.ts
src/renderer/src/components/ui/MessageDialog.vue
src/renderer/src/stores/dialog.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/App.vue
src/renderer/src/events.ts
src/renderer/src/components/ui/MessageDialog.vue
src/renderer/src/stores/dialog.ts

src/renderer/**/*.{vue,ts,js,tsx,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/project-structure.mdc)

渲染进程代码放在 src/renderer

Files:

src/renderer/src/App.vue
src/renderer/src/events.ts
src/renderer/src/components/ui/MessageDialog.vue
src/renderer/src/stores/dialog.ts

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/App.vue
src/renderer/src/events.ts
src/renderer/src/components/ui/MessageDialog.vue
src/renderer/src/stores/dialog.ts

**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (CLAUDE.md)

Strict type checking enabled for TypeScript

**/*.{ts,tsx}: 始终使用 try-catch 处理可能的错误
提供有意义的错误信息
记录详细的错误日志
优雅降级处理
日志应包含时间戳、日志级别、错误代码、错误描述、堆栈跟踪（如适用）、相关上下文信息
日志级别应包括 ERROR、WARN、INFO、DEBUG
不要吞掉错误
提供用户友好的错误信息
实现错误重试机制
避免记录敏感信息
使用结构化日志
设置适当的日志级别

Files:

src/renderer/src/events.ts
src/main/events.ts
src/main/presenter/index.ts
src/main/presenter/dialogPresenter/index.ts
src/shared/presenter.d.ts
src/renderer/src/stores/dialog.ts

**/*.{js,jsx,ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development-setup.mdc)

**/*.{js,jsx,ts,tsx}: 使用 OxLint 进行代码检查
Log和注释使用英文书写

Files:

src/renderer/src/events.ts
src/main/events.ts
src/main/presenter/index.ts
src/main/presenter/dialogPresenter/index.ts
src/shared/presenter.d.ts
src/renderer/src/stores/dialog.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/events.ts
src/main/events.ts
src/main/presenter/index.ts
src/main/presenter/dialogPresenter/index.ts
src/renderer/src/stores/dialog.ts

src/main/**/*.ts

📄 CodeRabbit Inference Engine (CLAUDE.md)

Main to Renderer: Use EventBus to broadcast events via mainWindow.webContents.send()

Use Electron's built-in APIs for file system and native dialogs

Files:

src/main/events.ts
src/main/presenter/index.ts
src/main/presenter/dialogPresenter/index.ts

src/main/**/*.{ts,js,tsx,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/project-structure.mdc)

主进程代码放在 src/main

Files:

src/main/events.ts
src/main/presenter/index.ts
src/main/presenter/dialogPresenter/index.ts

src/main/presenter/**/*.ts

📄 CodeRabbit Inference Engine (CLAUDE.md)

One presenter per functional domain

Files:

src/main/presenter/index.ts
src/main/presenter/dialogPresenter/index.ts

src/main/presenter/index.ts

📄 CodeRabbit Inference Engine (.cursor/rules/electron-best-practices.mdc)

The IPC messages from the main process to notify the view mainly rely on the EventBus index.ts to listen for events that need to be notified and then send them to the renderer through the mainWindow

Files:

src/main/presenter/index.ts

src/shared/**/*.ts

📄 CodeRabbit Inference Engine (CLAUDE.md)

Shared types in src/shared/

Files:

src/shared/presenter.d.ts

src/shared/*.d.ts

📄 CodeRabbit Inference Engine (.cursor/rules/electron-best-practices.mdc)

The shared/*.d.ts files are used to define the types of objects exposed by the main process to the renderer process

Files:

src/shared/presenter.d.ts

src/shared/**/*.{ts,tsx,d.ts}

📄 CodeRabbit Inference Engine (.cursor/rules/project-structure.mdc)

共享类型定义放在 shared 目录

Files:

src/shared/presenter.d.ts

src/renderer/src/stores/**/*.{vue,ts,tsx,js,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/pinia-best-practices.mdc)

src/renderer/src/stores/**/*.{vue,ts,tsx,js,jsx}: Use modules to organize related state and actions
Implement proper state persistence for maintaining data across sessions
Use getters for computed state properties
Utilize actions for side effects and asynchronous operations
Keep the store focused on global state, not component-specific data

Files:

src/renderer/src/stores/dialog.ts

🧠 Learnings (9)

📓 Common learnings

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/main/**/*.ts : Use Electron's built-in APIs for file system and native dialogs

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/renderer/src/composables/usePresenter.ts : The IPC in the renderer process is implemented in usePresenter.ts, allowing direct calls to the presenter-related interfaces exposed by the main process

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/{main,renderer}/**/*.ts : Implement proper inter-process communication (IPC) patterns

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/main/presenter/index.ts : The IPC messages from the main process to notify the view mainly rely on the EventBus index.ts to listen for events that need to be notified and then send them to the renderer through the mainWindow

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.{ts,tsx,vue} : Renderer to Main: Use usePresenter.ts composable for direct presenter method calls

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/vue-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:47:28.788Z
Learning: Applies to src/renderer/src/**/*.{vue,ts,tsx,js,jsx} : Implement proper state management with Pinia

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.{ts,tsx,vue} : Use Pinia for frontend state management

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/main/**/*.ts : Main to Renderer: Use EventBus to broadcast events via mainWindow.webContents.send()

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/llm-agent-loop.mdc:0-0
Timestamp: 2025-07-21T01:46:52.865Z
Learning: Applies to src/main/presenter/llmProviderPresenter/index.ts : `src/main/presenter/llmProviderPresenter/index.ts` should manage the overall Agent loop, conversation history, tool execution via `McpPresenter`, and frontend communication via `eventBus`.

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.vue : Add proper error handling and loading states for new UI components

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/vue-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:47:28.788Z
Learning: Applies to src/renderer/src/**/*.{vue,ts,tsx,js,jsx} : Use the Composition API for better code organization and reusability

src/renderer/src/App.vue (15)

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.vue : Add proper error handling and loading states for new UI components

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.vue : Follow existing component patterns in src/renderer/src/ when creating new UI components

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.vue : Use Composition API with proper TypeScript typing for new UI components

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/vue-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:47:28.788Z
Learning: Applies to src/renderer/src/**/*.{vue,ts,tsx,js,jsx} : Use the Composition API for better code organization and reusability

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/i18n.mdc:0-0
Timestamp: 2025-07-21T01:46:30.344Z
Learning: Applies to src/renderer/src/**/* : Use the 'vue-i18n' framework for all internationalization in the renderer

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/vue-shadcn.mdc:0-0
Timestamp: 2025-06-23T13:06:15.335Z
Learning: Utilize Nuxt's auto-imports feature for components and composables to reduce boilerplate.

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.vue : Use Composition API for all Vue 3 components

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.vue : Organize components by feature in src/renderer/src/

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/vue-shadcn.mdc:0-0
Timestamp: 2025-06-23T13:06:15.336Z
Learning: Import the Icon component from '@iconify/vue' and use it for rendering icons in Vue components.

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/vue-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:47:28.788Z
Learning: Applies to src/renderer/src/**/*.{vue,ts,tsx,js,jsx} : Leverage Vue's built-in reactivity system for efficient data handling

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/vue-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:47:28.788Z
Learning: Applies to src/renderer/src/**/*.{vue,ts,tsx,js,jsx} : Utilize Vue Router for navigation and route management

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/main/presenter/configPresenter/**/*.ts : Centralize configuration in configPresenter/

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/renderer/src/**/*.{ts,tsx,vue} : Renderer to Main: Use usePresenter.ts composable for direct presenter method calls

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/error-logging.mdc:0-0
Timestamp: 2025-07-21T01:46:19.681Z
Learning: Applies to **/*.{ts,tsx} : 提供用户友好的错误信息

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/error-logging.mdc:0-0
Timestamp: 2025-07-21T01:46:19.681Z
Learning: Applies to **/*.tsx : 使用错误边界捕获渲染错误

src/renderer/src/events.ts (9)

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/shared/.d.ts : The shared/.d.ts files are used to define the types of objects exposed by the main process to the renderer process

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-21T01:45:33.768Z
Learning: Applies to src/main/**/*.ts : Main to Renderer: Use EventBus to broadcast events via mainWindow.webContents.send()

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/main/**/*.ts : Use Electron's built-in APIs for file system and native dialogs

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/{main,renderer}/**/*.ts : Implement proper inter-process communication (IPC) patterns

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/main/presenter/index.ts : The IPC messages from the main process to notify the view mainly rely on the EventBus index.ts to listen for events that need to be notified and then send them to the renderer through the mainWindow

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/llm-agent-loop.mdc:0-0
Timestamp: 2025-07-21T01:46:52.865Z
Learning: Applies to src/main/presenter/llmProviderPresenter/index.ts : The main Agent loop should send standardized STREAM_EVENTS (RESPONSE, END, ERROR) to the frontend via eventBus.

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/llm-agent-loop.mdc:0-0
Timestamp: 2025-07-21T01:46:52.865Z
Learning: Applies to src/main/presenter/llmProviderPresenter/streamEvents.ts : Standardized stream events should conform to the LLMCoreStreamEvent interface, ideally defined in a shared file such as src/main/presenter/llmProviderPresenter/streamEvents.ts.

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/{main,renderer}/**/*.ts : Use context isolation for improved security

Learnt from: CR
PR: ThinkInAIXYZ/deepchat#0
File: .cursor/rules/electron-best-practices.mdc:0-0
Timestamp: 2025-07-21T01:45:54.217Z
Learning: Applies to src/main/eventbus.ts : eventbus.ts is primarily used for intercommunication between main processes and decouples modules with events

src/main/events.ts (8)