-
Notifications
You must be signed in to change notification settings - Fork 61
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
refactor: interchainstaking/keeper
#330
Conversation
Any idea why no checks have run here, @aljo242 ? |
Was wondering the same thing - no idea |
@joe-bowman running now after I merged |
Codecov Report
@@ Coverage Diff @@
## main #330 +/- ##
==========================================
- Coverage 55.33% 54.46% -0.88%
==========================================
Files 155 157 +2
Lines 11649 11689 +40
==========================================
- Hits 6446 6366 -80
- Misses 4745 4870 +125
+ Partials 458 453 -5
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@aljo242 bunch of conflicts now! |
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.
lgtm
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.
LGTM
1. Summary
interchainstaking
is our most complicated module and package in the codebase. This PR attempts to refactor and modularize thekeeper
package. Maintenance like this can help us with adding features, instrumentation and testing moving forward.2.Type of change
3. Implementation details
types
packageZone
struct as a pointer to our functions4. How to test/use
Verify functionality is not modified by this PR.
5. Checklist
6. Limitations (optional)
7. Future Work (optional)