-
Notifications
You must be signed in to change notification settings - Fork 2
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: debug multiple account request #580
Changes from all commits
3a30e36
6503134
f38dec1
a3391e9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -62,7 +62,17 @@ export const StakingContractDetails = ({ | |
); | ||
} | ||
|
||
if (!list || list.length === 0) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fixes another.mov |
||
return ( | ||
<Alert | ||
message="No staking information available." | ||
type="error" | ||
showIcon | ||
/> | ||
); | ||
} | ||
|
||
return ( | ||
<InfoBreakdownList list={list!} parentStyle={{ gap: 12 }} color="primary" /> | ||
<InfoBreakdownList list={list} parentStyle={{ gap: 12 }} color="primary" /> | ||
); | ||
}; |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -68,7 +68,8 @@ const useAllStakingContractDetails = () => { | |
{} as Record<string, Partial<StakingContractDetails>>, | ||
); | ||
|
||
const isAllStakingContractDetailsLoaded = queryResults.every( | ||
// TODO: some are failing, not sure why. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can be due to forks/testnets There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, but "every" still doesn’t feel right. I think we should just remove the failed ones. |
||
const isAllStakingContractDetailsLoaded = queryResults.some( | ||
(query) => query.isSuccess, | ||
); | ||
|
||
|
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.
ahh interesting, love such hacks :D
but ideally would store a reference to the new value (or a state), update it inside the handleSelectAgent right after updating the store value, and then in a separate useEffect would check the value from store, compare it with the ref (or state) and call all the below
but this fine with me too, so approving
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.
I think it was the same as what you are mentioning 🙈 , but adding a delay is a better than overcomplicating things with two states pointing to the same value and keeping them in sync. WDYT?
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.
it's not pointing to the same values, it's just the matter of synchronising them :D something similar to what we do on login when checking if the onboarding wasn't complete. just hope 0.5 sec delay is 100% stable