Fix/isValidMessage

[code-october]

💻 变更类型 | Change Type

• [x] feat
• [ ] fix
• [ ] refactor
• [ ] perf
• [ ] style
• [ ] test
• [ ] docs
• [ ] ci
• [ ] chore
• [ ] build

🔀 变更说明 | Description of Change

• 增加错误响应的判断（检测是否为包含 error 字段的 json）
• 总结历史的请求也判断消息是否异常

📝 补充信息 | Additional Information

Summary by CodeRabbit

• New Features

  • Introduced message validation to ensure only valid messages are processed for summarization.
  • Enhanced session management with improved uniqueness of session and message identifiers.

• Bug Fixes

  • Updated logic to prevent invalid messages from affecting session memory.

• Chores

  • Refined migration logic for older sessions to ensure consistent configurations.

[vercel[bot]]

@code-october is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai[bot]]

Walkthrough

The changes in this pull request primarily enhance the message handling and session management functionality within the app/store/chat.ts file. A new function, isValidMessage, is introduced to validate messages based on specific criteria. This function is integrated into the summarizeSession method to ensure only valid messages are processed. Additionally, the migration logic for session data is refined to improve the uniqueness of identifiers and to maintain consistency in session configurations.

Changes

File	Change Summary
app/store/chat.ts	- Added isValidMessage function to validate messages.
	- Updated summarizeSession to use isValidMessage for message validation.
	- Refined migration logic for session IDs using nanoid().
	- Set default values for compressModel and compressProviderName in session configuration.
test/isValidMessage.test.ts	- Added tests for the isValidMessage function covering various message scenarios.

Possibly related PRs

• #5522: This PR introduces a validation check for messages in the same app/store/chat.ts file, adding a function isValidMessage that aligns with the validation logic implemented in the main PR.

Suggested reviewers

• Dogtiti
• lloydzhou

Poem

🐇 In the chat where messages flow,
A new check to help us know,
If a message's fit to share,
Validity handled with care.
With unique IDs, our sessions gleam,
In the world of chat, we dream! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between dd793e0833ed49458212cd41b48a9bd89303b55b and fe9c31c3b761d4c5388698f84444bb094f24266a.

📒 Files selected for processing (1)

• test/isValidMessage.test.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• test/isValidMessage.test.ts

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

[github-actions[bot]]

Your build has completed!

Preview deployment

[Dogtiti]

下个版本会加上jest，到时可以更新主分支加一点测试用例方便review ~

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Jest will be added to the next version. At that time, the main branch can be updated and some test cases can be added to facilitate review ~

[Dogtiti]

可以更新一下代码，目前主分支已经加上了jest，可以补充一些测试用例~

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

You can update the code. Currently, jest has been added to the main branch. You can add some test cases~

[code-october]

测试用例暂时还不太清楚怎么添加，目前就是想覆盖这类错误提示，消息类型是不带json语言注释的代码块，其中包含error.message 字段：

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

It’s not yet clear how to add test cases. Currently, I just want to cover this type of error prompt. The message type is a code block without json language annotation, which contains the error.message field:

[Dogtiti]

可以将你这个函数导出 然后在test文件夹下参考有一个测试示例 目的是看你这里的修改能覆盖哪些情况

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

You can export your function Then refer to a test example in the test folder

[Dogtiti]

#5759