Repository navigation
fix(chat): show unread badges on selected conversations - #1278
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Since Colorado-Mesh#1278, renderer-ui shard 3/3 fails on main (and so on every PR that runs the full suite). The new "keeps selected channel unread visible until read" cases render the whole Chat panel twice and take 2-5 s each on their own, so the 5 s default times them out under a full shard's load; locally, `pnpm run check:pr` times out four of the six. locale-quality runs the whole i18n checker in a child process, about 5 s alone, and times out the same way. Both get a 30 s limit. No test logic changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EHFPfW7vZXpRdR3tBBTX3r
Selected channels and DMs hid their unread badges even when the saved read position still left messages unread. The App sidebar continued to count those messages, so a selected channel could look clear while the sidebar showed 69 unread. Selected conversation-picker rows also hid unread counts and MECP severity.
Show the computed unread count on selected channel pills, DM pills, and picker rows until an actual read action advances the watermark. Include DM counts in accessible names. Keep the picker's existing aggregate of other conversations.
This follows the badge/Catch up discrepancy reported alongside #1277. That PR fixes Catch up's saved-read-position fallback; this independent change fixes badge presentation. The screenshot alone does not establish the cause of Zeva's particular persistent count.
Validation:
pnpm run check:pr: lint, all type checks, and 15,980 passing tests (5 skipped).Summary by CodeRabbit