-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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(x/staking): Migrate LastValidatorPower to Collections #17498
Conversation
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
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 see the reader of types.LastValidatorPowerKey
is updated in this PR, but not the writer. Did I get that right? Is that done in a separate PR?
I don't understand. Does the changes for |
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
…ita/lastValPowerKey
Oh I definitely missed that on my first pass of this PR. |
@@ -51,6 +51,7 @@ type Keeper struct { | |||
RedelegationsByValDst collections.Map[collections.Triple[[]byte, []byte, []byte], []byte] | |||
RedelegationsByValSrc collections.Map[collections.Triple[[]byte, []byte, []byte], []byte] | |||
UnbondingDelegationByValIndex collections.Map[collections.Pair[[]byte, []byte], []byte] | |||
LastValidatorPower collections.Map[[]byte, []byte] |
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 have to say that I would find useful if we can add comments next to the field précising what is expected as key and as value. Right now, it is really not clear that we expect until I look deeper in the code.
I believe this would be a good practice to start doing when we simply use byte slices.
Description
Closes: #16376
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
make lint
andmake test
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