Conversation
Render provenance details as Summary, TRACE, Sources, and Execution sections for faster readability, especially on mobile. Keep raw JSON as an optional debug/fallback section within Discord length limits and preserve fail-open behavior when metadata is partial/unavailable. Add interaction tests for section rendering, long-payload truncation, and backend metadata failure fallback.
…ance details Use explicit unknown-to-ButtonInteraction casts at provenance details test call sites to satisfy strict structural typing expected by pnpm review. Keeps test-only behavior unchanged while restoring PR compatibility checks.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 11 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughRefactored Discord bot's provenance details rendering from JSON serialization to structured markdown sections (Summary, Trace, Sources, Execution, Raw JSON debug) with truncation support for Discord's 2000-character message limit. Added comprehensive test coverage including happy path, oversized payload truncation, and error handling scenarios. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 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 |
Escape source link text and URL delimiters in provenance details markdown rendering so titles with ] and URLs with ) do not break link syntax. Add regression coverage in provenanceButtons tests for escaped citation title/url output.
What changed
packages/discord-bot/src/interactions/button/provenanceButtons.ts.packages/discord-bot/test/provenanceButtons.test.tsfor:ButtonInteractiontest casting compatibility).Why this was changed
This aligns the Discord Trace Details UX with the task goal: users should quickly understand why an answer was generated without parsing dense payloads. The update improves readability (especially on mobile), keeps continuity with TRACE/provenance transparency goals, and still supports power-user debugging through optional raw payload visibility.
Important implementation details
This PR was written using Vibe Kanban
Summary by CodeRabbit
Release Notes
Refactor
Tests