Repository navigation
fix(account): show Unfillable warning for swap-and-bridge orders - #7701
fairlighteth merged 9 commits into
Conversation
The OrderFillabilityWarning was rendered only inside the regular-order branch of ActivityDetails, so bridge orders with insufficient allowance or balance had no warning in the Account modal even though their fillability state was already computed. Hoist the warning into a shared node and render it after both branches (BridgeActivitySummary and the regular layout) so bridge orders surface the same insufficient balance/allowance state as regular orders. Resolves cowprotocol#6803.
|
@tenderdeve is attempting to deploy a commit to the cow-dev Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reached
More reviews will be available in 12 minutes and 36 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 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 configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Walkthrough
ChangesFillability Warning Shared Across Order Types
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
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 |
…unfillable-warning
|
Cloudflare Pages preview mirror Preview branch URL: https://github.com/cowprotocol/cowswap/tree/cf-preview/pr-7701 Source fork branch:
|
fairlighteth
left a comment
There was a problem hiding this comment.
✅ AI Review (Codex GPT-5, worked 4m): no new findings
Review completed. I found no new non-duplicate comments worth posting.
Related context checked
- Current head:
9b433b8829bd. - Diff scope: one-file change in
apps/cowswap-frontend/src/modules/account/containers/Transaction/ActivityDetails.tsx. - The fix reuses the existing
OrderFillabilityWarningnode for both regular and bridge order layouts; the regular-order path keeps the same warning rendering. - Linked issue
#6803asks for the missing swap-and-bridge insufficient balance/allowance row, and the existing human review says this works. - No review threads were collected, and CodeRabbit had no actionable comments.
Generated using the pr-review skill from the CoW Protocol skills repo.
🧪 Scoped browser QA passed: mocked unfillable-warning matrix; live Safe/RPC not exercisedOutcome
Run details
Coverage matrix
Artifacts
Matrix screenshot:
How to retest
Not checked / follow-up
Generated using the |
✅ Security Review (Codex GPT-5, worked 13m): no verified security findingsReview completed. I found no verified security findings worth posting. Review scope and related context
Generated using the |
Resolve the Account activity conflict by keeping the shared fillability warning for bridge and regular orders while preserving the new approve-modal output amount from develop.
d310086 to
d72433a
Compare

Summary
Closes #6803.
In
ActivityDetails, theOrderFillabilityWarning(the "Unfillable" row that surfaces insufficient balance/allowance on a pending order) was rendered only inside the regular-order branch. WhenisBridgeOrderwas true the component routed toBridgeActivitySummaryand the warning block was skipped entirely — even thoughusePendingOrdersFillability()already produced the same fillability info for bridge orders, so the data was there but never displayed.Hoist the warning into a shared
fillabilityWarningnode and render it after both layouts so swap-and-bridge orders show the same insufficient balance / insufficient allowance state as regular orders.Test plan
Summary by CodeRabbit