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
feat(GUI): adding availability score in wallet #1118
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1118 +/- ##
==========================================
- Coverage 81.40% 81.40% -0.01%
==========================================
Files 173 173
Lines 9217 9216 -1
==========================================
- Hits 7503 7502 -1
Misses 1359 1359
Partials 355 355 |
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.
Adding GetAvailabilityScore
to wallet is not a good practice.
We can pass node
to walletModel
to get validator info. Then we can even show if validators in unbonded or last sortition height as well
|
||
valAddr, err := crypto.AddressFromString(info.Address) | ||
if err == nil { | ||
val := model.node.State().ValidatorByAddress(valAddr) |
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.
val itself has availability_score
. right?
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.
no, validator type does not contain an availability_score.
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.
You can get AvailabilityScore
from val
Description
Related issue(s)