Skip to content

feat: broom button to clear finished transfer rows#30

Merged
baronunread merged 1 commit into
baronunread:mainfrom
f4nu:clear-finished-transfers
Jul 20, 2026
Merged

feat: broom button to clear finished transfer rows#30
baronunread merged 1 commit into
baronunread:mainfrom
f4nu:clear-finished-transfers

Conversation

@f4nu

@f4nu f4nu commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds a small broom icon to the transfer widget header that clears only the finished rows (completed or failed transfers and moves), leaving anything still in flight.
  • Previously the only clear action was the close (X) button, which wipes the whole widget including in-flight rows.
  • The button appears only when there's at least one settled row to clear. It reuses the existing clearCompleted from MoveProgressContext for moves and dismisses settled transfers via the engine.

Test plan

  • bun run typecheck passes
  • bun test tests/unit/ui/MoveProgress.test.tsx tests/unit/ui/TransferWidget.test.tsx — 17 pass
  • Added a test asserting the broom sweeps a completed row while leaving an in-flight one

🤖 Generated with Claude Code

The transfer widget's only clear action was the close button, which
wipes everything including in-flight rows. Add a broom icon (shown only
when there's something finished to clear) that sweeps away just the
settled rows — completed or failed transfers and moves — and leaves
anything still running. Reuses the existing clearCompleted from
MoveProgressContext for moves.
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@f4nu, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 7 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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

How do review 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 refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ec1e0db0-8fa3-4c61-ae83-3d419de3d20d

📥 Commits

Reviewing files that changed from the base of the PR and between 69985cb and 9eb387c.

📒 Files selected for processing (2)
  • src/ui/TransferWidget.tsx
  • tests/unit/ui/MoveProgress.test.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.

@baronunread
baronunread self-requested a review July 20, 2026 21:12
@baronunread
baronunread merged commit 16e7ed2 into baronunread:main Jul 20, 2026
4 of 5 checks passed
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.

2 participants