stacklok / toolhive-studio / 26572732196

71%

main: 71%

Pull #2294

github

fix(use-toast-mutation): show error toast when successMsg is null

The entire `toast.promise(...)` call — including the `error:` branch —
was gated on `resolvedSuccessMsg !== null`, so any configured `errorMsg`
became dead code when callers passed `successMsg: null`. This silently
swallowed mutation errors in flows that legitimately suppress the
success toast (e.g. routes that navigate away on success) but still
want user-visible error feedback.

Register `toast.promise` whenever a success message or an error message
is configured, and only emit the `success:` key when applicable. The
silent-mode escape hatch (`successMsg: null` with no `errorMsg`) is
preserved.

Fixes #2293

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

5210 of 8004 branches covered (65.09%)

1 of 1 new or added line in 1 file covered. (100.0%)

7712 of 10933 relevant lines covered (70.54%)

115.06 hits per line