Fix/use balance stale closure comment

[greatKhalifa-code]

docs: clarify interval cleanup and refresh stability in use-balance

The balance polling interval in hooks/use-balance.ts was flagged as a potential stale closure bug. This PR adds explanatory comments confirming it is a
false positive:

• The clearInterval cleanup correctly captures the interval ID from its own effect scope — not a stale reference.
• refresh is stable because useCallback uses setTick with a functional updater, giving it no external dependencies.

closes #455

Summary by CodeRabbit

• Refactor
  • Refined code structure and event handling across mint and send features to improve maintainability.
  • Updated technical documentation for the balance tracking system.

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 55 minutes and 1 second. 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 refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d7b1a0b8-3f9e-4b13-8d96-69770300664b

📥 Commits

Reviewing files that changed from the base of the PR and between ffdd452 and 1677b38.

📒 Files selected for processing (1)

• hooks/use-balance.ts

📝 Walkthrough

Walkthrough

Three files are updated: app/mint/page.tsx and app/send/page.tsx each have inline onChange/onClick/onOpenChange lambdas replaced with named useCallback handlers. hooks/use-balance.ts receives only a comment update documenting interval cleanup and refresh callback stability.

Changes

useCallback Handler Memoization

Layer / File(s)	Summary
Mint page memoized input handlers app/mint/page.tsx	Adds useCallback import and three memoized handlers — handleFiatCurrencyChange, handleMintFiatAmountChange, and handleBurnAmountChange — then wires them to the fiat currency <select>, mint fiat <Input>, burn currency <select>, and burn amount <Input> in place of inline setters.
Send page memoized input and dialog handlers app/send/page.tsx	Adds handleContactChange, handleAmountChange, handleCustomRecipientChange, handleNoteChange, handleContinue, and handleConfirmDialogOpenChange as useCallback handlers; handleConfirmDialogOpenChange clears confirmedAmount when the dialog closes while sending is false. Wires all six handlers to their respective Select, Input, Button, and AlertDialog components.
use-balance interval cleanup comment hooks/use-balance.ts	Expands a single-line comment into a multi-line block that documents interval cleanup correctness and the stability of the refresh callback through useCallback with a functional state update.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Pi-Defi-world/acbu-frontend#258: Modifies how confirmedAmount is set and cleared in app/send/page.tsx when the confirm dialog opens and closes, overlapping directly with handleConfirmDialogOpenChange introduced here.
• Pi-Defi-world/acbu-frontend#259: Memoizes SendPage handlers and confirm dialog logic in app/send/page.tsx, the same refactor pattern applied in this PR.

Poem

🐇 Hop, hop, no more lambdas sprawled inline,
Each callback wrapped with useCallback — so fine!
The mint and send pages tidy and neat,
Memoized handlers make renders compete.
Even use-balance got a comment so bright,
This rabbit rejoices — the closures are right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR addresses issue #455 by documenting why the stale closure concern is a false positive in use-balance.ts, but also includes unrelated event handler refactoring in mint/page.tsx and send/page.tsx not mentioned in the linked issue.	The linked issue #455 only addresses use-balance.ts cleanup clarity, not event handler memoization in other components. Either remove out-of-scope changes or link additional issues.
Out of Scope Changes check	⚠️ Warning	Changes to app/mint/page.tsx and app/send/page.tsx introducing useCallback handlers for event optimization are not mentioned in issue #455, which focuses solely on use-balance.ts stale closure documentation.	Remove event handler refactoring from mint/page.tsx and send/page.tsx, or link additional issues that justify these changes.
Title check	❓ Inconclusive	The title refers to fixing a stale closure comment in use-balance, which is directly related to the use-balance.ts changes, but the PR also includes significant refactoring of event handlers in mint and send pages.	Consider revising the title to reflect all major changes, such as 'Add useCallback handlers and fix use-balance stale closure comment' or split into multiple PRs.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[drips-wave]

@greatKhalifa-code Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Junman140]

@greatKhalifa-code solve conflicts