chore: use overview generatedAt for card timestamp#30461
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 467932c. Configure here.
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection:
Why no E2E tags are needed:
Performance: No performance impact - this is a simple field assignment change with no rendering, data loading, or state management implications. Performance Test Selection: |
|




Description
The "What's Happening" carousel cards were showing article publish dates instead of a "generated" timestamp. The AI digest's
overview.generatedAtis a full ISO timestamp (2026-05-20T16:00:03.275Z) that accurately reflects when the content was last generated, giving users a consistent and correct relative time across all cards.Changelog
CHANGELOG entry: null
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Performance checks (if applicable)
trace()for usage andaddTokenfor an exampleFor performance guidelines and tooling, see the Performance Guide.
Pre-merge reviewer checklist
Note
Low Risk
Low risk: small, localized change to UI data mapping that only affects the displayed timestamp for carousel items, with tests updated to match.
Overview
Updates the
useWhatsHappeninghook so carousel item timestamps always use the market overview’sgeneratedAtvalue instead of per-article publish dates.Adjusts unit tests to assert the new timestamp behavior (and updates mock article date data accordingly).
Reviewed by Cursor Bugbot for commit 312181f. Bugbot is set up for automated code reviews on this repo. Configure here.