Files
Tomek Zawadzki e991e3f64f Keep the DeleteAccountDialog guard inside the try
Addresses review feedback on #11545. Hoisting the guard above the try moved the
throw past the catch, so a falsy did became an unhandled rejection with no
inline error, no log and no step reset.

Reverting outright would re-break compilation - confirmDeletion is a nested
callback of the component, so its throw is part of the same compiled unit. The
check stays where it was; only the throw and the optional chain move to a
module-scope requireAccount.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-25 17:35:15 +02:00
..
2026-08-25 17:26:43 +02:00
2026-03-25 00:50:26 -07:00