fix: use current session id to trigger rerender

[Dogtiti]

💻 变更类型 | Change Type

• feat
• fix
• refactor
• perf
• style
• test
• docs
• ci
• chore
• build

🔀 变更说明 | Description of Change

📝 补充信息 | Additional Information

Summary by CodeRabbit

• Improvements
  • Enhanced the Chat component to access the current session more reliably by using a unique session identifier.
  • Simplified the session reference for better stability during renders.

[vercel]

@Dogtiti is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The changes in this pull request focus on the Chat component within app/components/chat.tsx. The primary modification is the method of accessing the current session, shifting from using an index to directly retrieving the session object. This adjustment allows the component to be keyed by the session's unique identifier, enhancing stability during renders. No additional changes to logic or error handling were made.

Changes

File	Change Summary
app/components/chat.tsx	Updated session access from chatStore.currentSessionIndex to chatStore.currentSession(). The _Chat component is now keyed by session.id instead of an index.

Possibly related PRs

• feat: update real 'currentSession' #5765: Modifies the Chat component to enhance session summarization by passing the session object, related to the changes in session access.
• fix: updateCurrentSession => updateTargetSession #5774: Involves renaming session update methods, indicating a shift in session management that aligns with the current PR's focus.

Suggested reviewers

• lloydzhou

🐰 In the chat, we now see,
A session's key, as clear as can be!
No more index, just a unique ID,
Stability blooms, like a bright spring spree!
Hop along, let the chats flow,
With each new session, our joy will grow! 🌼

---

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.

[Dogtiti]

close #5792

[Issues-translate-bot]

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

---

close #5792

[Dogtiti]

修复新增聊天总是将currentSessionIndex设置为0 导致key没有变化所以组件没有重新卸载渲染导致的一系列相关问题

[Issues-translate-bot]

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

---

Fixed a series of related problems caused by always setting the currentSessionIndex to 0 when adding new chats, resulting in the key not changing and the component not being re-unloaded and rendered.

[github-actions]

Your build has completed!

Preview deployment

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

app/components/chat.tsx (1)

2074-2075: LGTM! Improved component stability using session ID.

The change from using an index to using the session's unique ID as the React key prop is a good improvement. This ensures stable component identity across rerenders and prevents potential issues with index-based keying when sessions are reordered or removed.

Consider adding a type annotation for better code clarity:

export function Chat() {
-  const session = chatStore.currentSession();
+  const session: ChatSession = chatStore.currentSession();
  return <_Chat key={session.id}></_Chat>;
}

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 38fa305 and 1d14a99.

📒 Files selected for processing (1)

• app/components/chat.tsx (1 hunks)