Skip to content

Update send_payment_along_path to take its args as struct #2370

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

Conversation

valentinewallace
Copy link
Contributor

@valentinewallace valentinewallace commented Jun 22, 2023

Cleans up and paves the way for additional arguments to be added more easily.

Edit: I thought this was helpful for route blinding, but it actually isn't. Still, I think it's a nice cleanup, so I'll keep it open.

Cleans up and paves the way for additional arguments to be added more easily,
specifically an update_add_htlc's blinding point.
Copy link
Contributor

@vladimirfomene vladimirfomene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review ACK 80f904c. It definitely makes the code cleaner.

Copy link
Contributor

@henghonglee henghonglee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK. definitely makes the code cleaner. I do have a small question about outbound_payment.rs

@@ -473,6 +473,18 @@ impl RecipientOnionFields {
}
}

/// Arguments for [`super::channelmanager::ChannelManager::send_payment_along_path`].
pub(super) struct SendAlongPathArgs<'a> {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Not so sure about the location of this struct. i'd think its supposed to be more co-located with where its used but i also think channelmanager.rs is also too large.

what is the current understanding around outbound_payment.rs? are we intending to move most/all outbound payment / routing / orchestration logic here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The outbound_payment module came about so we could remove code from channelmanager. So, anything exclusive to outbound payments (such as this struct) could reasonably live there IMO. I believe we've moved most if not all of it already.

@valentinewallace valentinewallace added the blocked on next release Should Wait Until Next Release To Land label Jun 29, 2023
@valentinewallace valentinewallace removed the blocked on next release Should Wait Until Next Release To Land label Jul 24, 2023
@TheBlueMatt TheBlueMatt merged commit c383f06 into lightningdevkit:main Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants