-
Notifications
You must be signed in to change notification settings - Fork 920
docs(generators): add community generators from Lexmata and PegasusHeavy #7803
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
Open
quinnjr
wants to merge
1
commit into
prisma:main
Choose a base branch
from
quinnjr:feature/add-community-generators
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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
🏁 Script executed:
Repository: prisma/web
Length of output: 447
Fix broken and outdated GitHub links before merge.
The link verification revealed two issues in this user-facing documentation:
prisma-ent-generatorreturns HTTP 404 — This repository is no longer accessible. Remove this entry or replace it with a working alternative if one exists.nestjs-prisma-graphqlhas moved owners — The repository redirects frompegasusheavytoquinnjr. Update the documentation to reflect the current owner:@quinnjr/nestjs-prisma-graphqlor verify if the package is still actively maintained.The
prisma-python-generatorlink is valid and requires no changes.🤖 Prompt for AI Agents
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.
This review is incorrect on both points:
prisma-ent-generatoris not a 404. The repository was private at the time of the review but has since been made public. It is now accessible at https://github.com/Lexmata/prisma-ent-generator.The
@pegasusheavyscope is correct. The npm package is published under@pegasusheavy/nestjs-prisma-graphql— that is the scope users install with. The GitHub redirect frompegasusheavytoquinnjris just because the GitHub username changed, but the npm package name and scope remain@pegasusheavy. No change is needed here.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.
Let me verify both of these claims before updating my assessment.
@quinnjr, you're absolutely right on both counts — I apologize for the incorrect review.@lexmata/prisma-ent-generator— The 404 was a false positive from the repository being private at the time of the automated link check. The npm package is verifiably real (it appears as a registered dependent of@prisma/generator-helper), and the repo is now public. No change needed.@pegasusheavy/nestjs-prisma-graphql— The@pegasusheavyscope is the correct and published npm package name. The GitHub redirect frompegasusheavy→quinnjris simply a result of a GitHub username change and does not affect the package identity or the documentation link. No change needed here either.All three entries are correct as written. The PR looks good from a link accuracy standpoint.
✏️ Learnings added