Skip to content
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

chore(perf): move SupplyStats logic to client side and remove state refresh #1935

Merged
merged 1 commit into from
Jul 5, 2024

Conversation

fuxingloh
Copy link
Contributor

Move SupplyStats request from client to server-side to reduce unnecessary waiting on server-side due to slowness. This allow part of the index to be loaded first without waiting for stats data to be resolved.

Also remove state refresh of that component that is triggered from central store.

Therefore improvement performance.

Copy link

netlify bot commented Jul 5, 2024

Deploy Preview for defi-scan ready!

Name Link
🔨 Latest commit f6f219f
🔍 Latest deploy log https://app.netlify.com/sites/defi-scan/deploys/6687bc45e0d3ee0008e3aa94
😎 Deploy Preview https://deploy-preview-1935--defi-scan.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@fuxingloh fuxingloh changed the title chore: move SupplyStats logic to client side and remove state refresh chore(perf): move SupplyStats logic to client side and remove state refresh Jul 5, 2024
@github-actions github-actions bot added the kind/chore Non feature change label Jul 5, 2024
@fuxingloh fuxingloh marked this pull request as ready for review July 5, 2024 09:36
@fuxingloh fuxingloh merged commit d59a745 into main Jul 5, 2024
15 of 16 checks passed
@fuxingloh fuxingloh deleted the fuxingloh/move-stats-to-client-side branch July 5, 2024 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/chore Non feature change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant