-
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
refactor(x/staking): migrate historicalInfo
to use collections
#17063
Conversation
historicalInfo
to use collectionshistoricalInfo
to use collections
…l-info-collections
…smos-sdk into ap/historical-info-collections
…l-info-collections
historicalInfo
to use collectionshistoricalInfo
to use collections
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.
We should also remove: IterateHistoricalInfo
. and also types.UnmarshalHistoricalInfo
.
Can GetAllHistoricalInfo
be removed also, I see it being used in a test only, so we can remove this method + the test?
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. Thanks.
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.
utACK
x/staking/keeper/historical_info.go
Outdated
@@ -123,7 +52,7 @@ func (k Keeper) TrackHistoricalInfo(ctx context.Context) error { | |||
} | |||
|
|||
historicalEntry := types.NewHistoricalInfo(sdkCtx.BlockHeader(), lastVals, k.PowerReduction(ctx)) | |||
|
|||
err = k.HistoricalInfo.Set(ctx, uint64(sdkCtx.BlockHeight()), historicalEntry) |
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.
nit: one liner
Description
ref: #14300
Closes: #16374
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