Repository navigation
bound reply chains in list output to 3 most recent - #83
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (4)
🔇 Additional comments (2)
Walkthrough
ChangesTodo reply display
Priority: ⬇️ Low Change: Bug fix Merge Risk: ⚪ Minimal · up to Todo lists show the three most recent replies and indicate how many earlier replies are omitted. No merge-blocking risk is evident. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Motivation
Issue #30: task-list responses expand long historical reply chains alongside current work, obscuring actionable state and consuming excessive tokens. The active-first ordering from #67 bounded completed todos but reply chains were still unbounded.
Solution
formatTodoList bounds each todo's reply chain to the 3 most recent replies with a count-prefixed omission indicator. Full history remains in durable state and is retrievable through explicit todo queries.
Validation
RED observed (test expected reply 12/11/10 visible and reply 9 absent with '9 earlier replies omitted'; failed against unbounded rendering). GREEN after: todo suite 59/59.
Summary by CodeRabbit