feat: add support for displaying legacy pre-parts array messages #103
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Added backward compatibility for messages using deprecated fields (body, thinkingContent, streamChunks). The UI now converts legacy message format to the new parts array format for proper display. Changes: - Handle legacy body field as text part - Convert thinkingContent to reasoning part - Process streamChunks into appropriate text/reasoning parts - Support deprecated messageType field for role determination - Handle deprecated timestamp field for message creation time This ensures all historical messages are displayed correctly in the UI. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
jeevanpillay
added a commit
that referenced
this pull request
Sep 3, 2025
- Update skeleton structure to match ServerSidebarImplementation layout - Add proper logo placeholder with correct dimensions - Match ActiveMenuItem and ThreadItem styling in skeleton - Improve user dropdown skeleton to show avatar and username placeholders - Use consistent overflow and width classes across all elements - Add two-line thread item skeletons for more realistic appearance This fixes the visual inconsistency during hard reloads by ensuring the skeleton closely matches the actual rendered sidebar components. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Added backward compatibility for displaying messages that use the deprecated/legacy format (pre-parts array).
Problem
After the merge, legacy messages stored with deprecated fields (like
body,thinkingContent,streamChunks) were not displaying in the UI because the conversion function only handled the newpartsarray format.Solution
Updated
convertDbMessagesToUIMessagesto handle both formats:partsarray (current standard)Legacy field mappings:
body→ text partthinkingContent→ reasoning partstreamChunks→ combined into text/reasoning parts based onisThinkingflagmessageType→ role (fallback for missingrolefield)timestamp→ createdAt (fallback for_creationTime)Testing
Impact
This ensures all historical chat messages are displayed correctly in the UI, regardless of which format they were stored in.
🤖 Generated with Claude Code