Add claimedRewardsEra to api.derive.staking.query for compatibility with legacyClaimedRewards #5862
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
StakingQueryFlags
Now takes in a new flag:
withClaimedRewardsEras
. This flag returns all the claimedRewards eras based on the new storage entryClaimedRewards
.api.derive.staking.electedInfo
:Adds a 3rd param for
page
.api.derive.staking.query
&&api.derive.staking.queryMulti
Returns a new field
claimedRewardsEras
whenwithClaimedRewardsEras
is true. This is for compatibility reasons for legacyClaimedRewards.Fix
api.derive.staking.stakingRewards
Now takes into account claimedRewards storage key to ensure all eras are accounted for.
TODO:
query
stakerRewards
electedInfo