chavic / rust-payjoin

86%

master: 86%

LAST BUILD ON BRANCH chavic/receive-error-kinds

branch: chavic/receive-error-kinds

CHANGE BRANCH

x

Reset

Sync Branches

• chavic/receive-error-kinds
• add-uniffi-dart-repo
• bech32-uppercase-assertion
• chavic/backup-uniform-primitive-types
• chavic/bdk-patch-regressions-fixes
• chavic/bindings-ci-lockfiles
• chavic/c-sharp-bindings
• chavic/csharp-devshell-binary-dotnet
• chavic/csharp-devshell-binary-dotnet-linux
• chavic/csharp-ffi-validation-catchup
• chavic/csharp-nix-devshell
• chavic/csharp-nuget-release-readiness-1448
• chavic/csharp-user-readme
• chavic/dart-fetch-ohttp-keys-https
• chavic/ffi-cleanup
• chavic/ffi-session-history-renaming
• chavic/ffi-string-impl-audit
• chavic/ffi-string-implementation-error-audit
• chavic/fix-ffi-devshell-followups
• chavic/fix-lint-result-large-err
• chavic/inputpair-outpoint-ffi
• chavic/json-reply-accessors-1271
• chavic/ohttp-hpke-error-variants-1273
• chavic/persisted-error-kind
• chavic/persisted-replay-errors-1275
• chavic/primitives-validatation-errors
• chavic/primitives-validatation-errors-old
• chavic/primitives-validation
• chavic/proposal-txid-stability
• chavic/psbt-input-error-index-1276
• chavic/receiver-error-variants-1270
• chavic/retry-expiration-metadata-1272
• chavic/substitution-contribution-errors-1277
• chavic/uniform-primities-types-backup16dec
• chavic/uniform-primitive-type-at-ffi-boundary-backup-after-rebase
• chavic/uniform-primitive-types-at-ffi-boundary
• chavic/uniform-primitive-types-at-ffi-boundary-8-12-2025-backup
• master
• replay-event-log-async
• spelling-fixes
• test/FetchOhttpKeys

Build # 29009312885

Build Type

push

github

Committed by chavic

Commit Message

Add kind accessors to receive candidate errors

CoinSelectionError and InputContributionError are opaque because
their variants may change, but that leaves callers of
try_preserving_privacy and contribute_inputs unable to distinguish
failures that could succeed with a different candidate set from
failures no candidate change can fix, short of matching display
strings. A wallet driving selection with a retry loop burns
attempts on the second class.

Add kind() returning a non_exhaustive kind enum on both errors:
callers get a stable, matchable classification while the error
types stay free to evolve, since new variants only require a new
kind category and consumers must already handle unknown kinds.
Mirror the accessors in payjoin-ffi with an explicit Other
catch-all, giving bindings the same signal; today these errors
cross the FFI as display-only objects.

Related to #1422.

Coverage Stats

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

13383 of 15581 relevant lines covered (85.89%)

349.9 hits per line