test: ErrorBoundary onError callback, reset key remount, TransactionPanel Try Again pre-filled form

[k-deejah]

Problem

Three test gaps cover the ErrorBoundary onError callback, reset key behaviour, and TransactionPanel "Try again" pre-filled form.

1. ErrorBoundary onError callback and production console suppression are untested

After issue #75, no test verifies: onError is called with the error and info when a child throws, console.error is not called in prod mode (import.meta.env.DEV = false), and the default log fires in dev mode.

2. ErrorBoundary reset key prevents the error loop

No test verifies that after reset(), the children are remounted (new component instance) rather than just re-rendered — preventing the same corrupted state from immediately re-throwing.

3. TransactionPanel "Try again" preserves form field values

After issue #71, the "Try again" button returns to the idle form with dest, amount, and memo pre-filled. No test verifies these values are preserved in the form inputs after "Try again" is clicked.

Solution

Write Vitest tests for all three behaviours.

Acceptance Criteria

• ErrorBoundary onError callback test passes
• ErrorBoundary reset key remount test passes
• TransactionPanel "Try again" pre-filled form test passes
• All tests pass with npm test

---

Note for Contributors: Write a clear PR description. Include the full npm test output and explain how you verified the reset key triggers a remount rather than a re-render.

[blockchainrafik]

@blockchainrafik has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day maintainer,
I will like to work on this issue,
With years of experience in software engineering, Getting this issue fixed without regression is assured.
ETA: 2hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @blockchainrafik to this issue.

[adeboladee]

@adeboladee has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer, Please I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @adeboladee to this issue.

[Benedict315]

@Benedict315 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Benedict315 to this issue.

[drips-wave]

Congratulations, @Benedict315! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Benedict315: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊