-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
fix: balance fetching bugs #10936
fix: balance fetching bugs #10936
Conversation
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
IMO, the balance should always match the current connect wallet. |
method: identityStore.fetchBalance if evm wallet is connected and you are on let me know if it makes sense. |
It's also what I want.
I'm not sure what you mean by the In short, the balances should always correspond to the type of wallet, regardless of the network prefix. |
covers case where wallet is disconnected and fetch is still in progress
Quality Gate passedIssues Measures |
pls @kodadot/internal-dev waiting for review 🥺 |
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.
work for me
PR Type
Context
Sub
wallet balance not loading whenevm
chain is selected #10933/base
the address is not formatted correctlyCleanShot.2024-09-06.at.12.10.40.mp4
vm
and chainvm
mismatch balance fetch usingidentityStore.fetchBalance
covers case where wallet vm and current chain's vm do not match, since prefix is unknown at that moment we are resorting to a fallbacks instate of not making a balance fetch
Example
evm wallet is connected , chain is ahp , navbar makes a balance fetch
this happens in the navbar and sidebar, in these scenarios what prefix should be fetched ?
@kodadot/internal-dev pls feel free to suggest any other solution.
Screenshot 📸
CleanShot.2024-09-06.at.12.05.08.mp4