-
Notifications
You must be signed in to change notification settings - Fork 420
Break up and function-ize handle_new_monitor_update
#4138
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
base: main
Are you sure you want to change the base?
Break up and function-ize handle_new_monitor_update
#4138
Conversation
We'll be breaking up this macro in upcoming commits.
Makes handle_new_monitor_update more readable.
Finishes work over the past few commits of breaking up the handle_new_monitor_update macro.
👋 Hi! I see this is a draft PR. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4138 +/- ##
==========================================
- Coverage 88.62% 88.60% -0.02%
==========================================
Files 180 180
Lines 134895 135247 +352
Branches 134895 135247 +352
==========================================
+ Hits 119546 119839 +293
- Misses 12587 12643 +56
- Partials 2762 2765 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
}}; | ||
} | ||
|
||
macro_rules! handle_new_monitor_update_todo_name { |
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.
handle_new_monitor_update_in_context
, because it pulls data from the given chan_context
?
Prefactor to some of @joostjager's experimental work including serialized channels in
ChannelMonitorUpdate
s as part of getting rid ofChannelManager
persistence.