You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a PaymentSent event in NodeEvents.kt but we also have another one in Peer.kt that extends the SendPaymentResult sealed class and contains more cases (PaymentNotSent and OfferNotPaid). But those are emitted on a different event flow (_eventsFlow). We should re-work those to provide a unified payment event interface emitted on a single event flow (maybe an event flow dedicated to payments would make sense?).
The text was updated successfully, but these errors were encountered:
Also, payInvoice() and payOffer() should have twins that immediately answer with a paymentId and do not wait for the payment to occur. Callers would rely on events to find out about payment attempts.
We have a
PaymentSent
event inNodeEvents.kt
but we also have another one inPeer.kt
that extends theSendPaymentResult
sealed class and contains more cases (PaymentNotSent
andOfferNotPaid
). But those are emitted on a different event flow (_eventsFlow
). We should re-work those to provide a unified payment event interface emitted on a single event flow (maybe an event flow dedicated to payments would make sense?).The text was updated successfully, but these errors were encountered: