Instead of _embed and breaking the posts to pages for pagination, actually handle pagination on the WP API level #42
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
…ually handle pagination on the WP API level
|
@aXlireza is attempting to deploy a commit to the 9d8 Team on Vercel. A member of the Team first needs to authorize it. |
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.
Neat stuff here, just couldn't side with getting all data via API and then doing the pagination beside the fact I'm not sure if for posts above 100 numbers whether it would be passed to the client.
I tweaked it, to handle page and perPage and Total pages by API(for some reason the total page and total posts numbers are in response header).
Had to change up the pagination UI a bit as well, ignore that and didn't have the patience for the type issue.