payjoin / rust-payjoin / 13355590759

83%

push

github

Handle receiver contribution errors as `unavailable` (#534)

Our reference must not panic if input contribution fails, but instead
show best practice for a non-automated receiver where the sender may
choose to try to payjoin again or broadcast the transaction extracted
from the original PSBT.

This is an implementation of my best idea for receiver error handling in
[my
comment](https://github.com/payjoin/rust-payjoin/issues/403#issuecomment-2651486357)
in #403

After this I think the only things to stabilize receiver errors is to
decide whether the single-variant `ContributionError` is correct and to
mark errors as non-exhaustive, and potentially expose variants as
public.

12 of 23 new or added lines in 3 files covered. (52.17%)

4007 of 5064 relevant lines covered (79.13%)

908.39 hits per line