Fix isClaimed in api.derive.staking.{stakerRewards, stakerRewardsMultiEras, stakerRewardsMulti} #6026
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.
The main problem was not taking the
isClaimed
field that was already calculated inparseRewards
and instead recalculating it infilterRewards
.I tested this against stash account:
13gMD93wc2P44QaVXRvThy1Q81846QKVovPBjZEWLzW9HnVR
. Which at the time had no reward for era 1623 claimed but had a reward claimed for 1622. So I tested it for [1623, and 1622] and logged theallRewards
inqueryMulti
in order to show the data being aggregated, and the final result. The results were as follows:Before:
After:
rel: polkadot-js/apps#11071