-
Notifications
You must be signed in to change notification settings - Fork 345
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
Correct outbound_payment
route-fetch calls to pass the hash + ID
#2092
Correct outbound_payment
route-fetch calls to pass the hash + ID
#2092
Conversation
`Route::get_route_with_id` exists to provide users payment-specific data when fetching a route, however we were failing to call it when we have such info, opting for the simple `get_route` instead. This defeats the purpose of the additional-metadata method, which we swap to using here.
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.
it's fine, but considering the amount of data find_route_with_id is returning, perhaps its return value should be a struct and not a tuple?
Codecov ReportPatch coverage:
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #2092 +/- ##
=======================================
Coverage 91.14% 91.14%
=======================================
Files 101 101
Lines 48887 48888 +1
Branches 48887 48888 +1
=======================================
+ Hits 44557 44559 +2
+ Misses 4330 4329 -1
... and 3 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
10e6978
Added another commit to further simplify the macro. The first commit here will be included in the 0.0.114.0 Java/Ts release, the second will not. |
Route::get_route_with_id
exists to provide users payment-specific data when fetching a route, however we were failing to call it when we have such info, opting for the simpleget_route
instead. This defeats the purpose of the additional-metadata method, which we swap to using here.