Reason: Would be nice to see as a user why a payment failed. We show a user their payment details in PaymentDetailView, leverages PaymentDetails which has PaymentStatus which looks like:
public enum PaymentStatus {
case pending
case succeeded
case failed
}
Where user should see this: User goes to main view and taps on payment to see the details. Right now they can see failed but no additional context.
Opened an Issue and draft PR on LDK Node. My suggestion is to add an associated reason to failed where we'd have access to something like:
public enum PaymentStatus {
case pending
case succeeded
case failed(<reason>)
}
Reason: Would be nice to see as a user why a payment failed. We show a user their payment details in
PaymentDetailView, leveragesPaymentDetailswhich hasPaymentStatuswhich looks like:Where user should see this: User goes to main view and taps on payment to see the details. Right now they can see
failedbut no additional context.Opened an Issue and draft PR on LDK Node. My suggestion is to add an associated reason to
failedwhere we'd have access to something like: