-
Notifications
You must be signed in to change notification settings - Fork 103
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
feat: add intertx module #1477
feat: add intertx module #1477
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1477 +/- ##
==========================================
- Coverage 78.72% 77.56% -1.16%
==========================================
Files 251 263 +12
Lines 18849 19244 +395
==========================================
+ Hits 14838 14926 +88
- Misses 3149 3453 +304
- Partials 862 865 +3
|
@@ -0,0 +1,53 @@ | |||
Feature: MsgRegisterAccount |
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.
would be nice to have a test case for amino sign bytes.
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.
added for MsgRegisterAccount e074640
dont think its possible for MsgSubmitTx though, since it contains protobuf.Any
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 MsgSubmitTx
's GetSignBytes
method panicking because, we need to register intertx
codec with every other modules RegisterLegacyAmino
method. We had a similar issue with SDK's governance module MsgSubmitProposal
13196.
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.
oof, that makes it impossible to use via amino right? that doesn't seem very good...
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.
Not sure if this will work. We can import all modules RegisterLegacyAminoCodec()
method and register with intertx
module codec.
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.
Looking good. Will need to figure out how to manually test. A few minor comments.
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.
Looking good. A few comments and a CHANGELOG entry.
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.
Looking good. Gave it a more thorough review and attempted some basic CLI testing.
Co-authored-by: Ryan Christoffersen <12519942+ryanchristo@users.noreply.github.com>
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.
tACK / utACK
Tested commands are implemented correctly and return expected errors. We will need to figure out the best means for manual testing (item included in v5.0 readiness checklist).
Nice work! Thanks for taking this on.
Description
adds the intertx module
Closes: #1453
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change