Posts Pagination #51
Merged
Posts Pagination #51
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 ↗︎
|
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.
Overview
As the number of posts has increased over time so has the size of the
/postspage. During deployment builds I started to see this warning.While the route loads fine in most cases, I understand that sending that data amount of data can have a larger impact on users with poor network connections. For that reason, I wanted to move away from statically generating the
/postspage.This PR updates the
/postspage to use client-side rendering and pagination to hydrate the page. During development, I also tried out server-side rendering, but I prefer to have most of the page load immediately and simply wait for the request to populate the posts section.