fix: Amendment Guard TokenEscrow preclaim#5473
Conversation
12063d9 to
8412f88
Compare
8412f88 to
c8c686f
Compare
| if (!slep) | ||
| return tecNO_TARGET; |
There was a problem hiding this comment.
This error needs to be thrown in doApply in both transactions
There was a problem hiding this comment.
It is already thrown in doApply for Cancel & Finish. It wasn't "moved" but rather copied.
There was a problem hiding this comment.
In that case, should the doApply one return tecINTERNAL if the amendment is enabled?
c8c686f to
a3ac092
Compare
62a4b63 to
dacc539
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #5473 +/- ##
=========================================
+ Coverage 79.0% 79.1% +0.1%
=========================================
Files 817 817
Lines 71739 71697 -42
Branches 8311 8240 -71
=========================================
+ Hits 56695 56708 +13
+ Misses 15043 14989 -54
+ Partials 1 0 -1
🚀 New features to boost your workflow:
|
| if (!ctx.view.rules().enabled(featureTokenEscrow)) | ||
| return temDISABLED; // LCOV_EXCL_LINE |
There was a problem hiding this comment.
I think it's fine to keep these blocks in just in case
This should bring it to 100% except for the JLOG in View.cpp? I can wrap those paths with a full LCOV? I didn't realize the log would trigger a non testable coverage. |
@dangell7 we normally use If you are uncertain if a line should be |
Re. already merged #5185 , I see the following deficiencies in unit tests coverage:
We have merge conflicts with other major features in flight (e.g. Lending #5270 ) and I would prefer if we had better assurance than "it compiles, all unit tests pass, but not all cases are tested" as an proof of good conflict resolution. |
Thank you for this review.
The return from Do you want me to create functional tests for this?
But... I believe it is possible inject a Escrow object into the open ledger and potentially write a test for this... I will work on that now but I did mark it excluded in case my idea doesn't work.
|
Bronek
left a comment
There was a problem hiding this comment.
nice, thank you for unit tests coverage cleanup !
No, it's cool. PS. apologies for editing your comment, I somehow confused the "reply" and "edit comment" function in Github, unintentionally abusing my maintainer privileges. 🙈 😳 Really sorry for this ! |
|
@dangell7 is the PR ready to merge? |
High Level Overview of Change
Context of Change
Type of Change
.gitignore, formatting, dropping support for older tooling)API Impact
libxrplchange (any change that may affectlibxrplor dependents oflibxrpl)