Skip to content

fix: wire up RaiseDisputeDialog in mobile CTA#306

Closed
lequangsang01 wants to merge 1 commit into
boundlessfi:mainfrom
lequangsang01:fix/mobile-raise-dispute-cta
Closed

fix: wire up RaiseDisputeDialog in mobile CTA#306
lequangsang01 wants to merge 1 commit into
boundlessfi:mainfrom
lequangsang01:fix/mobile-raise-dispute-cta

Conversation

@lequangsang01

Copy link
Copy Markdown

Summary

Brings the mobile Raise Dispute button to parity with the desktop sidebar by wiring up the existing RaiseDisputeDialog component.

Changes

  • Import RaiseDisputeDialog component
  • Add useState for disputeDialogOpen
  • Replace disabled "Coming Soon" button with enabled button that opens the dialog
  • Render RaiseDisputeDialog with proper props

Why

The mobile Raise Dispute button was a permanently disabled "Coming Soon" stub, but the flow already shipped in PRs #256 and #268. The desktop sidebar wires all of this up correctly. Mobile users currently have no way to raise a dispute because of the stale stub.

Closes #293

The mobile Raise Dispute button was a permanently disabled 'Coming Soon'
stub, but the flow already shipped in PRs boundlessfi#256 and boundlessfi#268. This wires up
the same RaiseDisputeDialog the desktop sidebar uses, bringing mobile
to parity with desktop.

Changes:
- Import RaiseDisputeDialog component
- Add useState for disputeDialogOpen
- Replace disabled button with enabled button that opens the dialog
- Render RaiseDisputeDialog with proper props

Closes boundlessfi#293
@vercel

vercel Bot commented Jun 27, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Threadflow Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jun 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@lequangsang01, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 59 minutes and 48 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c7582871-9a97-46d0-ac3f-9ffc4e757f51

📥 Commits

Reviewing files that changed from the base of the PR and between 9e5dc91 and 5ec4050.

📒 Files selected for processing (1)
  • components/bounty-detail/bounty-detail-mobile-cta.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mobile Raise Dispute CTA still shows "Coming Soon" — bring to parity with desktop sidebar

2 participants