Introduce Event Model for Offers Flow #3833
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the event-model for Flow, that allows a user to asynchronously examine, and handle and InvoiceRequest, or an Invoice, based on their selected
FlowConfig
.# Introduce Event Model for Offers FlowThis PR introduces an event-based model for
OffersMessageFlow
, enabling users to asynchronously examine and handle incomingInvoiceRequest
s orBolt12Invoice
s based on their configuredFlowConfigs
.By setting custom
FlowConfigs
, users can choose whether to:OfferEvents
for manual inspection and handling.This makes offer handling more flexible, especially in use-cases like:
The default configuration (
NeverTrigger
) maintains backward compatibility by preserving the existing synchronous behavior.