Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
Walkthrough
ChangesDailyStream focus refresh
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/desktop/src/components/daily-stream.tsx`:
- Around line 213-216: Update the savedScroll handling in daily-stream to clear
the focus refs and invoke republishFocusPending before returning whenever
savedScroll() returns a value, ensuring restored arrivals do not retain stale
autoFocus props. Add a regression test covering navigation away and back through
this restored-arrival sequence.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: cf3bb74a-4735-4b7b-8105-2c19f95911be
📒 Files selected for processing (1)
apps/desktop/src/components/daily-stream.tsx
A same-position arrival (e.g. re-navigating to today while the stream is already anchored there) writes the pending focus slot after the render pass and triggers no scroll, so the rows never re-read it; the stream now forces one pre-paint re-render per arrival, which also stabilizes the flaky webkit run of
daily-stream.focus.test.tsx.Summary by CodeRabbit