-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Index supply by denom #8517
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
Index supply by denom #8517
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8517 +/- ##
==========================================
+ Coverage 61.40% 61.42% +0.02%
==========================================
Files 674 671 -3
Lines 38397 38354 -43
==========================================
- Hits 23577 23559 -18
+ Misses 12336 12314 -22
+ Partials 2484 2481 -3
|
aaronc
left a comment
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 as long as we paginate GetTotalSupply in a follow up
Does it make sense to have seperate |
IMHO anywhere |
|
I agree with @aaronc. Please at the very least let's open a follow-up issue. |
|
@sahith-narahari please add a CHANGELOG entry too |
Sure, I'll make a followup issue. Should we also extend the same to GetAllBalances which is more widely used across other modules without pagination |
Yes, I think that makes sense too. |
|
Is a state migration needed for this? If yes, could you add one in |
Sure, I'll do it in the followup PR along with paginating supply. |
Yes it is. Could you add this to the tracking issue and reopen it @AmauryM ? |
|
|
||
| // Supply represents a struct that passively keeps track of the total supply | ||
| // amounts in the network. | ||
| message Supply { |
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.
This is a proto-breaking change. I'm okay to remove it in the v1beta2 package but not here.
I'm adding it back in the migration PR, and adding a deprecated comment to it.
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 can keep it in the proto files even though it's not used for now. Deprecated is the right step.
| ) | ||
|
|
||
| func TestDecodeStore(t *testing.T) { | ||
| t.Skip() |
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.
Is there a reason this test was skipped?
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.
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.
Oops sorry, this is unintended. Can you remove it in the store migration PR
Description
closes: #7092
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/)godoccomments.Unreleasedsection inCHANGELOG.mdFiles changedin the Github PR explorerCodecov Reportin the comment section below once CI passes