-
Notifications
You must be signed in to change notification settings - Fork 856
fix: get started page next button issue #7281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+2
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
1 change: 1 addition & 0 deletions
1
content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify that pagination_label is a recognized frontmatter field.
Line 4 adds
pagination_label: 'Quickstart'to establish the navigation label for this page, complementing thepagination_nextreference from the index page. The label is concise and appropriate. Ensure this field is recognized by your documentation platform's pagination/navigation system.Include the pagination_label field in the verification script above by looking for how it's used elsewhere:
🏁 Script executed:
Length of output: 27
🏁 Script executed:
Length of output: 3081
🏁 Script executed:
Length of output: 4429
🏁 Script executed:
Length of output: 779
Remove the unsupported
pagination_labelfield—it's not recognized by the documentation platform.The codebase uses
pagination_next(defined in the index file) to establish pagination flow, butpagination_labelis a new, undocumented field with no implementation. The official frontmatter specification (documented incontent/800-guides/999-making-guides.mdx) lists only:title,metaTitle,description,sidebar_label,image, andcommunity_section. Your docusaurus configuration contains no plugin or configuration to process custom pagination labels. This field will be silently ignored.The existing
pagination_next: getting-started/prisma-orm/quickstart/prisma-postgresin the index file already establishes the forward pagination link. Remove line 4 entirely.🤖 Prompt for AI Agents