docs(generators): add community generators from Lexmata and PegasusHeavy#7803
Conversation
The community generators list was missing several actively maintained generators that target non-JavaScript ecosystems and NestJS GraphQL: - @lexmata/prisma-ent-generator: produces Go Ent schema files - @lexmata/prisma-python-generator: produces Python Pydantic models - @pegasusheavy/nestjs-prisma-graphql: generates NestJS GraphQL types with ESM-first support targeting Prisma 7+
|
@quinnjr is attempting to deploy a commit to the Prisma Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
WalkthroughAdds three community Prisma generator entries to the docs and updates the docs' spell-check dictionary to include their names (preventing false-positive spelling flags). Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx`:
- Around line 399-401: Remove the broken `@lexmata/prisma-ent-generator` entry
(delete the line that references `prisma-ent-generator`) and update the
`@pegasusheavy/nestjs-prisma-graphql` entry to the current owner/package name
(`@quinnjr/nestjs-prisma-graphql`) and its GitHub URL; keep the
`@lexmata/prisma-python-generator` line unchanged. Ensure the text and link for
the NestJS package use `@quinnjr/nestjs-prisma-graphql` and the correct GitHub
repo URL so there are no redirects or 404s.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 7fdb57b4-539e-44c9-8738-f064065f6611
📒 Files selected for processing (1)
apps/docs/content/docs/orm/prisma-schema/overview/generators.mdx
|
could you add the following unknown words to this file here: https://github.com/prisma/web/blob/main/apps/docs/cspell.json. Currently the PR is failing because of that. |
…po URL CI was failing on the community-generators additions because cspell did not know the words `lexmata`, `Pydantic`, and `pegasusheavy`. Add each to apps/docs/cspell.json (alphabetically placed) so the spellcheck step passes. Also point the `@pegasusheavy/nestjs-prisma-graphql` link directly at github.com/quinnjr/nestjs-prisma-graphql instead of the legacy `pegasusheavy` username, which now redirects after a GitHub username change. The npm scope itself remains `@pegasusheavy` because that is the published package name; only the GitHub URL is updated to avoid the redirect hop.
|
@ankur-arch — added |
Summary
@lexmata/prisma-ent-generator— generates Go Ent schema files from Prisma schema@lexmata/prisma-python-generator— generates Python Pydantic model classes from Prisma schema@pegasusheavy/nestjs-prisma-graphql— generates NestJS GraphQL types from Prisma schema, ESM-first with Prisma 7+ supportTest plan
Summary by CodeRabbit