-
Notifications
You must be signed in to change notification settings - Fork 384
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
#2128 follow-ups #2801
#2128 follow-ups #2801
Conversation
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #2801 +/- ##
==========================================
- Coverage 88.46% 88.45% -0.01%
==========================================
Files 114 114
Lines 91806 91810 +4
Branches 91806 91810 +4
==========================================
- Hits 81214 81213 -1
- Misses 8112 8114 +2
- Partials 2480 2483 +3 ☔ View full report in Codecov by Sentry. |
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.
The name improvement looks great!
The new names InboundHTLCErr
, onion_cltv_expiry
, cltv_expiry_height
, and sender_intended_htlc_amt_msat
fit better in the context they are used while being clear with their functional usage.
Needs rebase, sorry about that. |
LGTM after rebase |
The prior name seems to reference onion decode errors specifically, when in fact the error contents are generic failure codes for any error that occurs during HTLC receipt.
There is no outgoing CLTV for received HTLCs, so this new var makes more sense.
.. since there is no outgoing cltv for received HTLCs.
There is no outgoing HTLC for received HTLCs, so rename to be more accurate.
There is no outgoing HTLC for received HTLCs, so rename to be more accurate.
There is no outgoing HTLC for received HTLCs, so rename to be more accurate.
9a0ed7b
to
b20a9ad
Compare
Rebased. |
Gonna land this with 1 ACK since it's trivial renames and at a glance I don't see any majorly conflicting PRs. Happy to rename further in follow-up if there's post-merge review. |
62d52c6
into
lightningdevkit:main
Very late follow-up from #2128. Just renames to be more descriptive.