feat(core): replace server-side api calls with client-side for list pages #298
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…yka/client-side-api-calls
lykalabrada
requested review from
thedoublejay,
kyleleow,
pierregee and
fullstackninja864
as code owners
DFC-119 Task: UI/UX Improvement - Tool tips
What UI/UX improvements need to be implemented?More information for tool tips Why is this needed?Users don't understand what it means Which component/screens does this concern? |
DFC-136 Performance: Improve speed of page redirects
In the current meta.defiscan.live, most of our API calls are done from the server side which is causing initial load to be slow and page switching to be clunky.
|
lykalabrada
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
In the current meta.defiscan.live, most of our API calls are done from the server side which is causing initial load to be slow and page switching to be clunky.
In this PR most API calls have been moved to the client side, this would allow our pages to be rendered right away before calling the APIs
on initial load, page is displayed right away, but users will see custom loaders for specific section (where api is not yet finished)
when switching page, users will see the loader right away instead of being stuck on the current page
Which issue(s) does this PR fixes?:
Fixes DFC-136
Additional comments?:
Developer Checklist: