✨ Expandable milestone rows & fix comment appending - #845
✨ Expandable milestone rows & fix comment appending#845AlejandroMinaya wants to merge 2 commits into
Conversation
After a public/private comment was posted, the resolved comment object was passed directly to afterSaveSuccess() as its queue argument. afterSaveSuccess() expected an array of callbacks and called .map() on it, causing a silent TypeError. More critically, flaw.value.comments was never updated, so the new comment was invisible until a full page reload. Fix: use the comment object already returned by postFlawComment to append it to flaw.value.comments, then call afterSaveSuccess() with no arguments matching its () => void signature. Test: 'should append the saved comment to flaw.value.comments'
manual_completion_notes was saved to the backend but never rendered. Add per-milestone expand/collapse rows (chevron toggle) that reveal: - Request Source - Request Received date - Request Text - Notes (manual_completion_notes) Clicking anywhere on the milestone row toggles the detail panel. Action buttons use @click.stop to avoid triggering the toggle. Keyboard accessible via Enter/Space. Tests: hidden by default, expands with content on click, collapses on second click.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe change adds expandable SRP milestone detail rows with keyboard-accessible actions and stronger typing. It also appends successfully saved OSIDB comments to the local flaw comment collection and adds test coverage for both behaviors. ChangesSRP milestone details
OSIDB comment state
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to Milestone rows can now reveal request and completion details, while newly saved comments appear immediately in local state. No merge-blocking risk is currently identified. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 3 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai resolve |
✅ Action performedComments resolved. Approval is disabled; enable |
Summary
Two changes for OSIDB-5497:
✨ Expandable milestone rows (SRPReportDetails)
manual_completion_noteswas saved to the backend but never rendered. Adds a per-milestone expand/collapse row (chevron toggle) that reveals:manual_completion_notes)Keyboard accessible via
Enter/Space. Falls back to "No additional details." when all fields are empty.🐛 Fix comment not appended after postFlawComment
After posting a public/private comment, the resolved comment object was passed directly to
afterSaveSuccess()as its queue argument.afterSaveSuccess()expected an array of callbacks and called.map()on it, causing a silent TypeError. More critically,flaw.value.commentswas never updated, so the new comment was invisible until a full page reload.Fix: use the comment object returned by
postFlawCommentto append it toflaw.value.comments, then callafterSaveSuccess()with no arguments matching its() => voidsignature.Tests
should append the saved comment to flaw.value.comments