Feat/stacking page #1774
Draft
Feat/stacking page #1774
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAttention: Patch coverage is 📢 Thoughts on this report? Let us know! |
BLuEScioN
force-pushed
the
feat/stacking-page
branch
from
967fd00 to
4a5c899
Compare
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.
Things I am noticing in this PR:
Sometimes we need to make a ton of requests in order to get all the data we need. If we had a backend we could make all those requests once on our backend, then cache the result, depending on the context, and serve that without having to ontinually hit the api. Pages where this makes sense would be signers, stacking page (pages that have data that is esentially static since it only changes every new cycle (2 weeks)