feat(blog): add Prisma Next ltree extension post#8085
Conversation
Publish community post on prisma-ltree for Prisma Next, plus Jason Procka author avatar and bio.
|
@slovakian is attempting to deploy a commit to the Prisma Team on Vercel. A member of the Team first needs to authorize it. |
WalkthroughAdds a technical blog post covering Prisma Next integration with PostgreSQL ChangesPrisma Next ltree blog
Estimated code review effort: 2 (Simple) | ~15 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
apps/blog/content/blog/prisma-next-ltree-extension/index.mdx (1)
161-161: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueConsider using a shorter alternative.
The phrase "by accident" can be simplified to "accidentally".
♻️ Proposed fix
-`*{1}` means exactly one label at that position, so `essays.*{1}` matches direct children such as `essays.drafts` and skips deeper paths like `essays.drafts.chapter_1`. A bare `essays.*` looks almost the same and is easy to type by accident, but `*` means zero or more labels, so it also matches `essays` itself and deeper paths like that grandchild. That footgun belongs to `lquery`, and the pack does not hide it. +`*{1}` means exactly one label at that position, so `essays.*{1}` matches direct children such as `essays.drafts` and skips deeper paths like `essays.drafts.chapter_1`. A bare `essays.*` looks almost the same and is easy to type accidentally, but `*` means zero or more labels, so it also matches `essays` itself and deeper paths like that grandchild. That footgun belongs to `lquery`, and the pack does not hide it.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/blog/content/blog/prisma-next-ltree-extension/index.mdx` at line 161, In the explanatory paragraph, replace the phrase “easy to type by accident” with the shorter wording “easy to type accidentally,” leaving the surrounding lquery behavior and examples unchanged.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/blog/content/blog/prisma-next-ltree-extension/index.mdx`:
- Line 45: Remove the low-level “use Node 24+” requirement from the introductory
setup guidance, while retaining the relevant `@prisma-next` version pin and setup
context in the pack overview.
- Line 10: Remove the unsupported heroImageAlt frontmatter property from the
blog post metadata, leaving the remaining frontmatter unchanged.
---
Nitpick comments:
In `@apps/blog/content/blog/prisma-next-ltree-extension/index.mdx`:
- Line 161: In the explanatory paragraph, replace the phrase “easy to type by
accident” with the shorter wording “easy to type accidentally,” leaving the
surrounding lquery behavior and examples unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 2351c464-e82b-4780-b779-0918c010d323
⛔ Files ignored due to path filters (3)
apps/blog/public/authors/jason-procka.pngis excluded by!**/*.pngapps/blog/public/prisma-next-ltree-extension/imgs/hero.svgis excluded by!**/*.svgapps/blog/public/prisma-next-ltree-extension/imgs/meta.pngis excluded by!**/*.png
📒 Files selected for processing (2)
apps/blog/content/blog/prisma-next-ltree-extension/index.mdxapps/blog/src/lib/author-bios.ts
| metaTitle: "Extending Prisma Next with Typed Postgres ltree" | ||
| metaDescription: "Use PostgreSQL ltree in Prisma Next with prisma-ltree: typed path columns plus ancestor and descendant queries." | ||
| heroImagePath: "/prisma-next-ltree-extension/imgs/hero.svg" | ||
| heroImageAlt: "Typed ltree for Prisma Next: the prisma-ltree extension pack shown as a hierarchical path tree" |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Remove unsupported frontmatter property.
The heroImageAlt property is not defined in the frontmatterSchema for blog posts in apps/blog/source.config.ts (as seen in Context snippet 1). Depending on the Zod schema's configuration, this will either be silently ignored during parsing or cause a build-time validation error.
♻️ Proposed fix
-heroImageAlt: "Typed ltree for Prisma Next: the prisma-ltree extension pack shown as a hierarchical path tree"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| heroImageAlt: "Typed ltree for Prisma Next: the prisma-ltree extension pack shown as a hierarchical path tree" |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/blog/content/blog/prisma-next-ltree-extension/index.mdx` at line 10,
Remove the unsupported heroImageAlt frontmatter property from the blog post
metadata, leaving the remaining frontmatter unchanged.
|
|
||
| ## Using `ltree` with Prisma Next | ||
|
|
||
| A pack is an extension package that contributes types, migrations, and runtime operators to Prisma Next. `prisma-ltree` plugs in the same way other Postgres extension packages do (`pgvector`, `postgis`). Setup is six steps. The samples below match the pack's `examples/family-tree` app: pin `@prisma-next/*` to `0.14.0` and use Node 24+. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Remove low-level system requirements.
Based on learnings, avoid including low-level compatibility or version-matrix details like "use Node 24+" unless those specifics materially improve correctness or prevent a real reader-facing misunderstanding. Consider removing the Node requirement to keep the guidance clear and actionable, as package managers typically handle engine requirements automatically.
♻️ Proposed fix
-A pack is an extension package that contributes types, migrations, and runtime operators to Prisma Next. `prisma-ltree` plugs in the same way other Postgres extension packages do (`pgvector`, `postgis`). Setup is six steps. The samples below match the pack's `examples/family-tree` app: pin `@prisma-next/*` to `0.14.0` and use Node 24+.
+A pack is an extension package that contributes types, migrations, and runtime operators to Prisma Next. `prisma-ltree` plugs in the same way other Postgres extension packages do (`pgvector`, `postgis`). Setup is six steps. The samples below match the pack's `examples/family-tree` app: pin `@prisma-next/*` to `0.14.0`.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| A pack is an extension package that contributes types, migrations, and runtime operators to Prisma Next. `prisma-ltree` plugs in the same way other Postgres extension packages do (`pgvector`, `postgis`). Setup is six steps. The samples below match the pack's `examples/family-tree` app: pin `@prisma-next/*` to `0.14.0` and use Node 24+. | |
| A pack is an extension package that contributes types, migrations, and runtime operators to Prisma Next. `prisma-ltree` plugs in the same way other Postgres extension packages do (`pgvector`, `postgis`). Setup is six steps. The samples below match the pack's `examples/family-tree` app: pin `@prisma-next/*` to `0.14.0`. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/blog/content/blog/prisma-next-ltree-extension/index.mdx` at line 45,
Remove the low-level “use Node 24+” requirement from the introductory setup
guidance, while retaining the relevant `@prisma-next` version pin and setup
context in the pack overview.
Source: Learnings
1 participant
Publish community post on prisma-ltree for Prisma Next, plus Jason Procka author avatar and bio.
Summary by CodeRabbit
New Content
Authors