[FLN-194][Hoang][UI] Fix chat and AI [17.11.2025]

[hofang42]

Overview

• Fix chat và update logic call api AI

---

Check list

Checklists

• Đã test đầy đủ trước khi tạo PR
• Đã tự review lại code
• Đảm bảo không commit các file không cần thiết (VD: .env, node_modules, build folder, v.v.)
• Đã đặt tên branch, commit theo đúng quy định
• Add Reviewers và Assignees
• Add Labels

---

Jira Ticket

https://flearning.atlassian.net/browse/FLN-194

---

EVD

[cursor]

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on December 7

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Improve null safety for _id access.

Calling .toString() on p._id assumes it's always an object with a toString method, but if p._id is already a string or if p is null/undefined, this will throw an error. The optional chaining on conv.participants?.find protects against participants being null, but not against individual participant objects or their _id properties being null/undefined.

 

[cursor]

Bug: Ensure _id Type Safety for toString Calls

Calling .toString() on p._id assumes it's always an object with a toString method, but if p._id is already a string or if p is null/undefined, this will throw an error. The optional chaining on conv.participants?.find protects against participants being null, but not against individual participant objects or their _id properties being null/undefined.

 

[cursor]

Bug: Conversation Data Structure Inconsistency

When spreading conversationData from the backend response, the data isn't formatted to match the frontend structure. The backend likely returns _id, last_message, etc., but the frontend expects id, lastMessage. While explicit properties like lastMessage and status override backend properties, _id from the backend will remain, causing the conversation object to have _id instead of or alongside id, breaking comparisons like conv.id === newConversationId throughout the codebase.

 

[cursor]

Bug: Conversation Data Structure Mismatch Breaks Frontend

When creating a new conversation from conversationData, the backend response is spread directly without formatting to match the frontend structure. The backend returns properties like _id, last_message, and participants with _id fields, but the frontend expects id, lastMessage, and properly formatted participant data. This inconsistency with the socket event handlers (lines 133-144, 162-173) will cause the new conversation to have mismatched property names, breaking functionality that relies on conv.id.