There is a small impact on the payments database, as the status of failed parts are stored using a code: Int json (with an optional String message).
@robbiehanson we should remove the details for failed parts on iOS. Instead, show a single error message using the OutgoingPaymentFailure.explain() method that will pick the most pertinent error for a given payment (will return either a FinalFailure error, or a Part.Status.Failure)
This PR supports the new outgoing payment failures types added in https://github.com/ACINQ/lightning-kmp/pull/634.
There is a small impact on the payments database, as the status of failed parts are stored using a
code: Intjson (with an optional String message).@robbiehanson we should remove the details for failed parts on iOS. Instead, show a single error message using the
OutgoingPaymentFailure.explain()method that will pick the most pertinent error for a given payment (will return either aFinalFailureerror, or aPart.Status.Failure)