fix(session): sort messages by time.created instead of alphabetical order #7425
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.
What does this PR do?
Fixes
Session.messages()to sort messages bytime.createdtimestamp instead of relying on alphabetical message ID order.Fixes #7426
Problem
opencode export <session_id>outputs messages in wrong order for long sessions. The first part of the conversation appears in the middle or end of the export.Root cause:
Session.messages()usedresult.reverse()which only reverses the alphabetical order fromStorage.list(). Message IDs are random strings (e.g.,msg_19b9ed*vsmsg_b9946c*), so alphabetical order ≠ chronological order.Fix
Replace
result.reverse()withresult.sort((a, b) => a.info.time.created - b.info.time.created)to ensure messages are always sorted by creation timestamp.How did you verify your code works?
lsp_diagnosticson changed file - no errors