Repository navigation
Conversation
|
The following comment was made by an LLM, it may be inaccurate: I found related PRs that may be worth reviewing: Related PRs:
These PRs are working on similar timestamp/time-display features in the TUI and may have relevant code patterns or logic that could affect the current PR. |
|
Thanks for the pointers. I reviewed both PRs:
No duplication — all three cover different timestamp surfaces. |
|
- Replace toContain('·') with toMatch on digit patterns so formatting
tweaks don't break tests
- Use fixed date with setHours instead of Date.now() to avoid
midnight race in CI
Co-Authored-By: zai-glm-52 <[email protected]>
Agent: @test
Scope: anomalyco#43243
|
Thanks for the review. All points addressed:
|
|
Any updates on this? I need this info to see whether the session KV cache is still alive or not 😅 |
|
This branch has been upgraded to V2. We're no longer taking PRs for V1. If you think this is still relevant, please port it over and open it for V2. — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊 |
Issue for this PR
Closes #43243
Type of change
What does this PR do?
The TUI already has a
/timestampstoggle that shows timestamps on user messages. This PR extends it to also showtime.createdin the assistant message footer, so both sides of the conversation get timestamps when the toggle is on.The change is 3 lines in
AssistantMessage— a<Show when={ctx.showTimestamps()}>block that rendersLocale.todayTimeOrDateTime(props.message.time.created)alongside the existing model name and duration. No new mode, no config changes, no data model changes. The toggle still defaults to "hide" (backward compatible).How did you verify your code works?
4 tests in
packages/tui/test/util/timestamps.test.tscoveringtodayTimeOrDateTime,time, anddatetimeformatting with locale-agnostic assertions.Screenshots / recordings
N/A
Checklist