-
-
Notifications
You must be signed in to change notification settings - Fork 38
docs: add missing customAttributesAsComments option to prisma plugin
#387
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe documentation has been updated in two main files: Changes
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
docs/reference/plugins/prisma.md (1)
26-26: Consider adding a code example for better clarity.To help users better understand the impact of this option, consider adding a before/after example showing how the schema looks with and without
customAttributesAsCommentsenabled.Example addition:
### Example ```zmodel title='/schema.zmodel' plugin prisma { provider = '@core/prisma' output = './src/prisma/schema.prisma' }
Example Output
- With
customAttributesAsComments: false(default):- model Post {
- id Int @id
- title String
- @@Allow('create', true)
- }
- With
customAttributesAsComments: true:- model Post {
- id Int @id
- title String
- // @@Allow('create', true)
- }
</blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: CodeRabbit UI** **Review profile: CHILL** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 8bde97053da825dbc51d98c8214c3cf54945b65c and c78c49637e4053d76d3c4abae77ff5c535034c7f. </details> <details> <summary>📒 Files selected for processing (2)</summary> * `docs/guides/edge.md` (1 hunks) * `docs/reference/plugins/prisma.md` (1 hunks) </details> <details> <summary>🔇 Additional comments (2)</summary> <details> <summary>docs/reference/plugins/prisma.md (1)</summary> `26-26`: **Documentation looks good and aligns with PR objectives!** The new option is well-documented with clear description, type, and default value. </details> <details> <summary>docs/guides/edge.md (1)</summary> `126-126`: **LGTM! Good addition about Hono integration.** The added reference to Hono integration provides valuable information for users looking to build more sophisticated backends on Cloudflare Workers. </details> </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
Summary by CodeRabbit
PrismaClientusage.@core/prismaplugin documentation to include a new option,customAttributesAsComments, for generating non-Prisma attributes as comments in the Prisma schema.