-
Notifications
You must be signed in to change notification settings - Fork 81
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: handling of token page throttling #1100
Conversation
The token page is prone to being throttled because it tries to load in order books for the "top 10 tokens". This change moves logic to useQuery and out of redux. It then makes sure the token's information is loaded in before trying to load in dex pairs. Fixes #790
}) | ||
|
||
it('should dispatch correct actions on successful loadTokenState', () => { | ||
client.addResponses(rippledResponses) |
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 might be worth having this tests still to check that rippled responses are transformed 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.
We can have a ticket to add these back later.
Seems like #984 might be related |
I think we can merge this one in first to fix token page. Then we can rebase the one that you created |
This reverts commit 8d503da.
High Level Overview of Change
The token page is prone to being throttled because it tries to load in
order books for the "top 10 tokens". This change moves logic to useQuery
and out of redux. It then makes sure the token's information is loaded
in before trying to load in dex pairs.
Fixes #790
Type of Change
TypeScript/Hooks Update
Before / After
Before
After