enh: Docs Checkbox Handling - #528
Conversation
Detect checklist items in Google Docs API responses and render them as - [ ] (unchecked) and - [x] (checked) in markdown, so LLMs understand checkbox state instead of writing literal [x] or DONE text. Closes #516 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughWalkthroughGoogle Docs to Markdown conversion now supports checklist lists with checked/unchecked item rendering. Two new helper functions detect checklists and checked items, while the text rendering pipeline accepts a skip_strikethrough flag to prevent redundant formatting on completed items. A new constant for shortcut field resolution was also added. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 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 |
|
Works nicely |
Checkboxes in Google Docs are read as plain bullet items, so the LLM doesn't know they're checkboxes and writes literal [x]/DONE text. The fix is in docs_markdown.py - detect checklist items and render them as - [ ]/- [x] in markdown.
Summary by CodeRabbit