Skip to content
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

merge dev to main (v2.9.1) #1877

Merged
merged 1 commit into from
Nov 19, 2024
Merged

merge dev to main (v2.9.1) #1877

merged 1 commit into from
Nov 19, 2024

Conversation

ymc9
Copy link
Member

@ymc9 ymc9 commented Nov 19, 2024

No description provided.

Copy link
Contributor

coderabbitai bot commented Nov 19, 2024

📝 Walkthrough

Walkthrough

This pull request includes two primary changes: an update to the version number in the build.gradle.kts file for the JetBrains plugin, changing it from 2.9.0 to 2.9.1, and modifications to the run function in the index.ts file of the Prisma plugin. The changes in index.ts enhance the logic for determining the path to the Prisma Client's TypeScript declaration file and improve error handling related to this resolution process.

Changes

File Path Change Summary
packages/ide/jetbrains/build.gradle.kts Version updated from 2.9.0 to 2.9.1. No other changes to dependencies or task definitions.
packages/schema/src/plugins/prisma/index.ts Enhanced logic for determining the Prisma Client's TypeScript declaration path with improved error handling.

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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 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

🧹 Outside diff range and nitpick comments (2)
packages/schema/src/plugins/prisma/index.ts (2)

85-105: LGTM! Consider enhancing the error message.

The new path resolution logic is robust and handles both custom output paths and node module resolution gracefully. However, the error message could be more specific about which resolution method failed.

Consider updating the error message to be more specific:

- `Could not resolve PrismaClient type declaration path. This may break plugins that depend on it.`
+ `Could not resolve PrismaClient type declaration path (tried custom output path and node module resolution). This may break plugins that depend on it.`

85-105: Consider extracting path resolution logic into a separate function.

The path resolution logic could be more maintainable if extracted into a dedicated function, improving readability and testability.

Consider refactoring like this:

function resolvePrismaClientDtsPath(
    schemaPath: string,
    clientOutputDir: string,
    customOutput?: string
): string | undefined {
    if (customOutput) {
        const customPath = path.resolve(path.dirname(schemaPath), clientOutputDir, 'index.d.ts');
        if (fs.existsSync(customPath)) {
            return customPath;
        }
    }

    try {
        const prismaClientResolvedPath = require.resolve(clientOutputDir, {
            paths: [path.dirname(schemaPath)],
        });
        return path.join(path.dirname(prismaClientResolvedPath), 'index.d.ts');
    } catch {
        return undefined;
    }
}

Then use it in the main code:

prismaClientDtsPath = resolvePrismaClientDtsPath(
    options.schemaPath,
    clientOutputDir,
    clientOutput
);

if (!prismaClientDtsPath) {
    console.warn(
        colors.yellow(
            `Could not resolve PrismaClient type declaration path. This may break plugins that depend on it.`
        )
    );
}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 76c6579 and c0b240c.

⛔ Files ignored due to path filters (13)
  • package.json is excluded by !**/*.json
  • packages/ide/jetbrains/package.json is excluded by !**/*.json
  • packages/language/package.json is excluded by !**/*.json
  • packages/misc/redwood/package.json is excluded by !**/*.json
  • packages/plugins/openapi/package.json is excluded by !**/*.json
  • packages/plugins/swr/package.json is excluded by !**/*.json
  • packages/plugins/tanstack-query/package.json is excluded by !**/*.json
  • packages/plugins/trpc/package.json is excluded by !**/*.json
  • packages/runtime/package.json is excluded by !**/*.json
  • packages/schema/package.json is excluded by !**/*.json
  • packages/sdk/package.json is excluded by !**/*.json
  • packages/server/package.json is excluded by !**/*.json
  • packages/testtools/package.json is excluded by !**/*.json
📒 Files selected for processing (2)
  • packages/ide/jetbrains/build.gradle.kts (1 hunks)
  • packages/schema/src/plugins/prisma/index.ts (1 hunks)
🔇 Additional comments (1)
packages/ide/jetbrains/build.gradle.kts (1)

12-12: LGTM: Version update aligns with release objectives

The version increment from 2.9.0 to 2.9.1 follows semantic versioning and matches the PR title for merging v2.9.1 to main.

packages/ide/jetbrains/build.gradle.kts Show resolved Hide resolved
@ymc9 ymc9 merged commit 38530b8 into main Nov 19, 2024
17 checks passed
This was referenced Dec 3, 2024
@coderabbitai coderabbitai bot mentioned this pull request Dec 25, 2024
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.

1 participant