Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
---
title: 'Quickstart with Prisma ORM and Prisma Postgres'
sidebar_label: 'Prisma Postgres'
pagination_label: 'Quickstart'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 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 the pagination_next reference 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:

#!/bin/bash
# Description: Check pagination_label usage patterns

# Find all uses of pagination_label in the docs
rg -n 'pagination_label' content/ --type mdx

Length of output: 27


🏁 Script executed:

#!/bin/bash
# Description: Find pagination_label usage and related pagination fields

# Search for pagination_label without type specification
echo "=== Searching for pagination_label ==="
rg -n 'pagination_label' content/

# Search for pagination_ prefix to understand the pattern
echo -e "\n=== Searching for other pagination_ fields ==="
rg -n 'pagination_' content/ | head -20

# Look for pagination_next to understand the bidirectional reference
echo -e "\n=== Searching for pagination_next ==="
rg -n 'pagination_next' content/

Length of output: 3081


🏁 Script executed:

#!/bin/bash
# Description: Verify if pagination_label is a supported field

# Look for docusaurus configuration
echo "=== Looking for Docusaurus config files ==="
find content/ -name "docusaurus.config.*" -o -name "sidebar*" -o -name ".docusaurus*" 2>/dev/null | head -10

# Look for any documentation about frontmatter or pagination
echo -e "\n=== Searching for pagination documentation in files ==="
rg -n 'pagination_label|frontmatter|supported.*field' content/ --type-not json | head -15

# Check root directory for config
echo -e "\n=== Checking repository root for config files ==="
ls -la | grep -E 'docusaurus|config|\.doc'

# Look for any TypeScript/JS config in root
echo -e "\n=== Looking for docusaurus config at root ==="
find . -maxdepth 2 -name "docusaurus.config.js" -o -name "docusaurus.config.ts" 2>/dev/null

Length of output: 4429



🏁 Script executed:

#!/bin/bash
# Description: Understand how pagination system works (pagination_next context)

# Search for any custom pagination handling or plugins
echo "=== Looking for custom pagination implementation ==="
rg -n 'pagination' . --type ts --type js -g '!node_modules' --type-not mdx | head -20

# Check if there's a client plugin or theme customization for pagination
echo -e "\n=== Checking client-plugins directory ==="
find . -path ./node_modules -prune -o -type f -name "*pagination*" -print

# Look at a file that uses pagination_next to understand context
echo -e "\n=== Context around pagination_next usage ==="
rg -B 5 -A 5 'pagination_next' content/100-getting-started/index.mdx | head -20

# Check if pagination_label appears in any theme or plugin files
echo -e "\n=== Searching entire repo for pagination_label (not just content/) ==="
rg -n 'pagination_label' . -g '!node_modules' 2>/dev/null || echo "Only in target file"

Length of output: 779


Remove the unsupported pagination_label field—it's not recognized by the documentation platform.

The codebase uses pagination_next (defined in the index file) to establish pagination flow, but pagination_label is a new, undocumented field with no implementation. The official frontmatter specification (documented in content/800-guides/999-making-guides.mdx) lists only: title, metaTitle, description, sidebar_label, image, and community_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-postgres in the index file already establishes the forward pagination link. Remove line 4 entirely.

🤖 Prompt for AI Agents
In
content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
around line 4, remove the unsupported frontmatter field "pagination_label:
'Quickstart'" entirely; ensure the surrounding frontmatter remains valid YAML
(no stray commas or broken separators) and rely on the existing pagination_next
in the index file for navigation.

metaTitle: 'Quickstart: Prisma ORM with Prisma Postgres (5 min)'
metaDescription: 'Create a new TypeScript project from scratch by connecting Prisma ORM to Prisma Postgres and generating a Prisma Client for database access.'
---
Expand Down
1 change: 1 addition & 0 deletions content/100-getting-started/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ metaDescription: 'Build data-driven applications with ease using Prisma ORM, add
hide_title: true
sidebar_position: 0
sidebar_class_name: firstTitle
pagination_next: getting-started/prisma-orm/quickstart/prisma-postgres
---

import {
Expand Down
Loading