Skip to content

Add note about prisma-json-types-generator in docs #1617

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

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

goleary
Copy link
Contributor

@goleary goleary commented Jan 15, 2025

✅ Checklist

  • I have followed every step in the contributing guide
  • The PR title follows the convention.

Summary by CodeRabbit

  • Documentation
    • Updated configuration documentation for Prisma extension
    • Added clarification about clientGenerator option when using multiple generators
    • Included example of prisma-json-types-generator configuration

Copy link

changeset-bot bot commented Jan 15, 2025

⚠️ No Changeset found

Latest commit: 1a41518

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Jan 15, 2025

Walkthrough

The documentation for trigger.config.ts has been updated to provide clearer guidance on configuring Prisma extensions, specifically focusing on the clientGenerator option. The changes aim to help developers understand how to manage multiple generators in a Prisma schema file, with an emphasis on preventing unintended generator outputs and demonstrating the configuration of additional generators like prisma-json-types-generator.

Changes

File Change Summary
docs/config/config-file.mdx Added explanatory note about clientGenerator option for Prisma schema configurations

Poem

🐰 A Rabbit's Config Tale 🔧
In Prisma's garden of generators bright,
With clientGenerator, we set things right
No extra clients shall slip through the gate
Our schema's config now sits straight and great!
Hop to precision, with clarity's might! 🌟


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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
docs/config/config-file.mdx (1)

Line range hint 452-471: Consider adding comments to explain the generator configurations.

While the example is good, it would be more helpful with inline comments explaining:

  • Why you might use prisma-kysely
  • What the output configuration options mean
 generator client {
   provider        = "prisma-client-js"
+  // This is the default Prisma Client generator
 }

 generator kysely {
   provider     = "prisma-kysely"
+  // Generates TypeScript types for Kysely query builder
   output       = "../../src/kysely"
   enumFileName = "enums.ts"
   fileName     = "types.ts"
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5eb30d0 and 1a41518.

📒 Files selected for processing (1)
  • docs/config/config-file.mdx (2 hunks)
🔇 Additional comments (2)
docs/config/config-file.mdx (2)

449-450: LGTM! Clear explanation of the clientGenerator option.

The explanation effectively communicates the purpose and use case of the clientGenerator option, helping users understand when they might need it.


Line range hint 476-492: LGTM! Clear configuration example.

The trigger.config.ts example clearly demonstrates how to specify the clientGenerator option.

Comment on lines +472 to +474
generator json {
provider = "prisma-json-types-generator"
}
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add explanation for prisma-json-types-generator.

The example introduces prisma-json-types-generator without context about its purpose or benefits.

 generator json {
+  // Generates TypeScript types for JSON fields in your schema
   provider = "prisma-json-types-generator"
 }
📝 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.

Suggested change
generator json {
provider = "prisma-json-types-generator"
}
generator json {
// Generates TypeScript types for JSON fields in your schema
provider = "prisma-json-types-generator"
}

@matt-aitken
Copy link
Member

Thanks :)

@matt-aitken matt-aitken merged commit 2ad664d into triggerdotdev:main Jan 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants