-
Notifications
You must be signed in to change notification settings - Fork 116
Add reason to Event::PaymentFailed and Event::ChannelClosed
#260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add reason to Event::PaymentFailed and Event::ChannelClosed
#260
Conversation
573e0dc to
311c500
Compare
reason to Event::PaymentFailedreason to Event::PaymentFailed and Event::ChannelClosed
3358062 to
c4b53d5
Compare
c4b53d5 to
1aab36a
Compare
|
FWIW, flaky Python test should be unrelated. |
6704dad to
f697dc7
Compare
jkczyz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please squash.
.. which declutters our `lib.rs` imports a bit.
f697dc7 to
a062cb2
Compare
Squashed the fixup without further changes. |
jkczyz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any thoughts on including the reason in PaymentStatus?
Yeah, maybe we should, although I kind of like the simplicity of |
Fixes #259.
Fixes #247.
To provide some more insight why a payment failed, we expose the
PaymentFailureReasonin our event. We also expose thereasoninChannelClosed.