Fix Pagination Navigation in "Get Started" Section #6173
Closed
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
|
Hi there, Thank you so much for your contribution, but we actually just resolved this. Really appreciate your time and if you see any issues, please let us know! |
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.
Description
This PR addresses the pagination issues in the Getting Started section by updating the front matter of each MDX file to include the
pagination_prevfield.Issue Details
The "Previous" navigation buttons were self-referential so it was not possible to go back on most pages. In most cases clicking Previous reloaded the Typescript/Postgres version of the current page no matter what language/database configuration the user was in. The buttons worked on a few of the title pages but not in nested routes. This PR allows navigation back and forth through the docs and maintains the user's choices where possible. (There are a couple of cases where there is a missing Planetscale page so the Postgresql version was chosen in those cases.)