Repository navigation
fix(order-progress): match countdown to reduced solve deadlines - #7888
Conversation
|
@tenderdeve is attempting to deploy a commit to the cow-dev Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThe order progress bar now uses 10 seconds on mainnet and 7 seconds on other supported chains. Chain ID is propagated through progress bar components to calculate the circular countdown duration. ChangesProgress countdown
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant Backend
participant OrderProgressBar
participant SolvingTopSection
participant CircularCountdown
Backend->>OrderProgressBar: backend status becomes ACTIVE
OrderProgressBar->>OrderProgressBar: select duration from chainId
OrderProgressBar->>SolvingTopSection: pass countdown and chainId
SolvingTopSection->>CircularCountdown: pass countdown and chainId
CircularCountdown->>CircularCountdown: render network-specific progress
Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@tenderdeve , please rebase the PR to develop |
Progress bar countdown is now 10s on mainnet and 7s on all other chains, instead of a flat 15s, so orders no longer show several seconds left on the clock when they are already settled. The circular countdown scales to the same per-chain duration.
240bdfc to
a27cceb
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
kernelwhisperer
left a comment
There was a problem hiding this comment.
LGTM, thank you!
|
|
||
| interface SolvingTopSectionProps { | ||
| countdown: number | ||
| chainId: OrderProgressBarProps['chainId'] |
There was a problem hiding this comment.
Nitpick: this could be SupportedChainId
| stepName: OrderProgressBarProps['stepName'] | ||
| order: OrderProgressBarProps['order'] | ||
| countdown: number | ||
| chainId: OrderProgressBarProps['chainId'] |
There was a problem hiding this comment.
Nitpick: this could be SupportedChainId
elena-zh
left a comment
There was a problem hiding this comment.
Hey @tenderdeve , thank you for addressing it!
|
@kernelwhisperer updated in d06c5df — typed |
Closes #7808
The order progress bar countdown was a flat 15s on every chain, so orders were shown with several seconds still on the clock after they had already settled under the reduced solve deadlines.
This sets the countdown to 10s on mainnet and 7s on all other chains, via a
getProgressBarTimerDuration(chainId)helper. The circular countdown animation uses the same per-chain duration so its scale stays correct.Summary by CodeRabbit