-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Update auth cli commands #6717
Update auth cli commands #6717
Conversation
… into sahith/update-auth-cli
Codecov Report
@@ Coverage Diff @@
## master #6717 +/- ##
==========================================
+ Coverage 55.60% 61.64% +6.04%
==========================================
Files 457 511 +54
Lines 27440 31893 +4453
==========================================
+ Hits 15257 19662 +4405
+ Misses 11083 10676 -407
- Partials 1100 1555 +455 |
This pull request introduces 1 alert when merging d1eb8c1 into 6f928e1 - view on LGTM.com new alerts:
|
… into sahith/update-auth-cli
One comment I would make is that it has been suggested that we should use different encoding and application types and convert between the two. |
One other subtle difference is between the |
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.
it has been suggested that we should use different encoding and application types and convert between the two
OK, this point also makes sense. in this case I'll approve, the migration to use the new TxConfig looks good 🎉
I still think some work can be done in terms of clarity with all these signing types, though maybe it's as simple as better naming. I can take a look in the next couple of days, after this PR gets merged.
Thanks @amaurymartiny. That would be great. |
types/tx/signing/signature.go
Outdated
// SignatureDataToSignatureDescriptorData converts a SignatureData to SignatureDescriptor_Data. | ||
// SignatureDescriptor_Data is considered an encoding type whereas SignatureData is used for | ||
// business logic. | ||
func SignatureDataToSignatureDescriptorData(data SignatureData) *SignatureDescriptor_Data { |
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.
I do agree here. I'd go with what @amaurymartiny stated or at the very least, change the nomenclature because it's confusing and the types clobber each other.
This pull request introduces 1 alert when merging 423cbcb into 2da954f - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging 0136c11 into 2da954f - view on LGTM.com new alerts:
|
@alexanderbez I think we've addressed your comments here. |
* add utils * update sign cmd * update multisign cmd * update sign batch cmd * update genutil cmd * add wrap tx builder * update gentx cli * update validate sigs cmd * fix lint * add flag reader to cli * update marshaler for batchscan * add register query server * update to master * remove depricated methods * fix keyring issue * update wraptx * Fix batch scan * fix register interfaces issue * update printOutput * Update Validate Sigs test * WIP on signature JSON * Cleanup * Cleanup * Test fixes * Test fixes * Fixes * WIP on tests * Fix gov tests * fix lint * fix MultiSign tests * fix tests * refactor tests * Cleanup * Address review comments * Update encode * Test fix * Rename SignData func * Fix lint * Fix lint * Revert ReadTxCommandFlags Co-authored-by: Aaron Craelius <aaron@regen.network> Co-authored-by: Aaron Craelius <aaronc@users.noreply.github.com>
Description
Ref: #6213
This is part of breakdown of #6216 into smaller PRs
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes