feat:Modify the knowledge base interface

[lichunn]

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Background and solution

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Improvements
  • Updated search functionality to improve query processing and data retrieval efficiency.

[coderabbitai]

Walkthrough

The search functionality in the robot plugin Vue component has been updated to use a new vector-storage API endpoint (/app-center/api/vector-storage/search) instead of the previous AI search endpoint, with expanded request payloads that include content data and a collection identifier for document references.

Changes

Cohort / File(s)	Change Summary
Search API Migration packages/plugins/robot/src/Main.vue	Updated search endpoint from /app-center/api/ai/search to /app-center/api/vector-storage/search in two locations; expanded request payload to include content field and collection: 'tinyengine_documents' metadata

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A hop, skip, and API change away,
From old search paths to vector realms we play,
With tinyengine documents in tow,
The storage grows where knowledge flows,
Two endpoints merged, one cleaner way! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title "Modify the knowledge base interface" is related to the changeset's subject matter but lacks specificity about the actual technical changes. The pull request involves replacing a search API endpoint and expanding the request payload structure, but the title uses generic language ("Modify", "interface") that doesn't clearly convey what was specifically changed. While the title isn't unrelated to the changes, it's too vague for a developer scanning commit history to understand that this involves switching from one API endpoint to another or that the payload structure was expanded.	Consider using a more specific title that clearly describes the primary technical change, such as "Update search API endpoint to vector-storage backend" or "Replace AI search API with vector storage search endpoint". This would help teammates understand the core change at a glance and make the commit history more informative.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c27e843 and d483d9d.

📒 Files selected for processing (1)

• packages/plugins/robot/src/Main.vue (1 hunks)

⏰ 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: push-check

🔇 Additional comments (1)

packages/plugins/robot/src/Main.vue (1)

497-500: Verify response format compatibility with new vector-storage endpoint and improve error handling.

The endpoint migration from /app-center/api/ai/search to /app-center/api/vector-storage/search is complete—no references to the old endpoint were found in the codebase. The search function is appropriately isolated to a single usage location (line 569) and only executes when aiType.value === AI_MODES['Builder'].

However, verify that the new endpoint returns an array of objects with a content property, as the response handling at line 502 assumes this structure. If the actual response format differs, the code will fail silently.

Additionally, the empty catch block at lines 505-507 means search failures occur silently. Consider logging errors or notifying users when knowledge base search fails, as this could degrade AI response quality without any visible indication.

Suggested improvement for error handling:

     } catch (error) {
-      // error
+      console.error('Knowledge base search failed:', error)
+      Notify({
+        type: 'warning',
+        message: '知识库搜索失败，AI回复可能不够准确',
+        position: 'top-right',
+        duration: 3000
+      })
     }

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}