-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Remove the old message PublicKey proto oneof #7390
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7390 +/- ##
=======================================
Coverage 55.33% 55.33%
=======================================
Files 587 587
Lines 36502 36502
=======================================
Hits 20200 20200
Misses 14204 14204
Partials 2098 2098 |
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.
Left one comment to change wording.
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! small wording proposals
Co-authored-by: Amaury Martiny <amaury.martiny@protonmail.com>
@@ -2,33 +2,9 @@ syntax = "proto3"; | |||
package cosmos.base.crypto.v1beta1; |
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.
@blushi would it actually make sense to remove this proto file, and put the 2 remaining messages inside cosmos.crypto.multisig
?
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.
yes I believe that makes sense.
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.
moved the proto file to proto/crypto/multisig
but kept the generated types in crypto/types
because:
- putting it in
crypto/keys/multisig
wouldn't make much sense ; - it would introduce some import cycles.
@@ -0,0 +1,25 @@ | |||
syntax = "proto3"; | |||
package cosmos.crypto.multisig.v1beta1; |
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.
Should we remove v1beta1
here? I believe in cosmos.crypto.*
we kind of decided not to put any v1beta1 anywhere
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 made sense to remove the versioning for PubKey
types which are then used to generate addresses but it might be better to keep it for MultiSignature
and CompactBitArray
like it's the case for the rest of the proto types.
Co-authored-by: Amaury Martiny <amaury.martiny@protonmail.com>
// CompactBitArray is an implementation of a space efficient bit array. | ||
// This is used to ensure that the encoded data takes up a minimal amount of | ||
// space after proto encoding. | ||
// This is not thread safe, and is not intended for concurrent usage. |
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.
Could you provide a link in the comment to the encoding spec?
Description
ref: #7357
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