Repository navigation
fix: render both label and value for DISPLAYTEXT feedback - #14
Conversation
RuleFeedbackList (playground) and the shared FormFeedback components each rendered only one half of a DISPLAYTEXT rule's feedback (content or value, never both), so rules that combine a static label with computed data silently dropped one side. The mui FormFeedback was worst-hit, rendering a completely empty alert for value-less DISPLAYTEXT rules. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughWalkthroughFeedback rendering now checks whether ChangesFeedback rendering
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)
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 |


Summary
RuleFeedbackList(playground) rendered onlycontentforDISPLAYTEXTfeedback, silently dropping the rule's computeddata/valuewhenever a rule set both a static label and dynamic data.FormFeedbackcomponents (dhis2-ui,mantine,mui) had the mirror-image bug — rendering onlyvalue, droppingcontent.mui's was worst-hit: a value-lessDISPLAYTEXTrule (the common case, just a static message) rendered a completely empty, invisible alert.contentalone when there's no dynamic value, orcontent: valuewhen there is, matching the intendedDISPLAYTEXTsemantics already covered byutils/rules/src/evaluate.test.ts.Test plan
pnpm exec vitest run utils/rules— 21/21 pass, unchanged (data contract untouched)tsc --noEmitclean ondhis2-ui,mantine,mui, andapps/playgroundprettier -cclean on all four changed filesDISPLAYTEXTrule that setsdata— not verified in this environment (no reachable instance/credentials)🤖 Generated with Claude Code
Summary by CodeRabbit