fix: show milestone receivers on milestone cards#68
Conversation
|
Someone is attempting to deploy a commit to the Trustless Work Team on Vercel. A member of the Team first needs to authorize it. |
|
Worried about impact? Review this PR in Change Stack to explore blast radius before you approve or request changes. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThis PR adds per-milestone receiver display to the Escrow Viewer. The receiver data model is extended in the mapper, extracted from multi-release escrow contracts, threaded through milestone card props, rendered with address truncation, and wired into both desktop and mobile view paths. ChangesMilestone Receiver Data Threading
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
Summary
receiverto normalized multi-release milestones.receiver(with compatible fallbacks forreceiver_address,recipient, andrecipient_address).Contract storage note
The issue identifies
receiveras the current milestone-level receiver field; this implementation reads that field first and keeps fallback names only for schema compatibility.Verification
npx tsc --noEmitnpm run build(passes; existing Next/Stellar dependency warnings about dynamicrequireremain)git diff --checkCloses #65
Summary by CodeRabbit