Standardize thread timestamps to compact relative format - #3945
Conversation
Threads rendered a raw wall-clock time (e.g. "3:45pm") while spaces/channels show a compact relative timestamp (e.g. "3w", "11m"). Point ThreadTimestamp at the shared formatRelativeTimeShort helper so both surfaces match. The absolute date/time is still available in the hover tooltip. Generated-By: PostHog Code Task-Id: 0e5947d9-11d5-41a7-b9b0-25d102bbf4f8
|
😎 Merged successfully - details. |
|
React Doctor found no issues in the changed files. 🎉 Reviewed by React Doctor for commit |
|
✅ Visual changes approved by @jonathanlab — baseline updated in 8 new. |
jonathanlab
added
the
Stamphog
PostHog
|
Reviews (1): Last reviewed commit: "Standardize thread timestamps to compact..." | Re-trigger Greptile |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Trivial 3-line UI formatting change swapping a local timestamp formatter for an existing shared helper; diff matches description, no risky territory involved.
- 👍 on the PR from greptile-apps[bot].
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 3L, 1F substantive — within ceiling |
| tier | ✓ | T1-agent / T1a-trivial (3L, 1F, single-area, unknown) |
| stamphog 2.0.0b3 | .stamphog/policy.yml @ dd419cf · reviewed head 296813a |
8 updated Run: a22e4ab5-20c2-4c20-868e-d22ef6f7a814 Co-authored-by: jonathanlab <32547391+jonathanlab@users.noreply.github.com>
|
/trunk merge |
New commits pushed (delta classified non_trivial_delta) — stamphog approval dismissed; re-review running automatically.
There was a problem hiding this comment.
Small, contained UI change swapping a local timestamp formatter for an existing shared helper, with matching snapshot updates already visually approved; no risky territory involved.
- Author wrote 0% of the modified lines and has 96 merged PRs in these paths (familiarity MODERATE).
- 👍 on the PR from greptile-apps[bot].
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 19L, 2F substantive — within ceiling |
| tier | ✓ | T1-agent / T1b-small (19L, 2F, two-areas, unknown) |
| stamphog 2.0.0b3 | .stamphog/policy.yml @ d2aa7b7 · reviewed head 37e1db4 |
1 participant
Problem
Threads didn't use the same timestamp format as spaces/channels. Channels show a compact relative time (e.g.
3w,11m), but threads rendered a raw wall-clock time (e.g.3:45pm), so the two surfaces looked inconsistent.Why: Requested so threads read the same way as spaces/channels.
Changes
ThreadTimestampnow rendersformatRelativeTimeShortfrom@posthog/shared— the same helper channels/spaces already use — instead of its local wall-clock formatter. This one change covers every thread surface (thread messages, artifacts, and activity/user-message rows) since they all funnel throughThreadTimestamp. The absolute date/time remains available in the hover tooltip.How did you test this?
pnpm --filter @posthog/ui test ThreadPanel— 13 passing.@posthog/ui; no errors in the package.Automatic notifications
Created with PostHog Code