chore(prisma): upgrade prisma to v5.19.0

[steebchen]

Upgrade prisma to v5.19.0 with engine hash 5fe21811a6ba0b952a3bc71400666511fe3b902f.
Full release notes: v5.19.0.

Summary by CodeRabbit

• New Features

  • Updated Prisma CLI and Engine versions to enhance functionality and performance.
  • Introduced a structured approach for transforming response data, improving clarity and maintainability.

• Bug Fixes

  • Improved response data transformation, ensuring better integrity and format handling in the application.

• Tests

  • Enhanced test coverage and clarity for the response transformation functionality, ensuring robustness against various data scenarios.

[coderabbitai]

Walkthrough

The recent changes involve updating version constants in binaries/version.go, with PrismaVersion incremented to "5.19.0" and EngineVersion updated to a new commit hash. The transformResponse function in engine/transform.go has been overhauled for enhanced JSON processing, introducing a new Input type. The corresponding test suite in engine/transform_test.go has been adjusted for improved coverage. Additionally, a new dependency on the engine package has been introduced in runtime/transaction/result.go to process response data.

Changes

Files	Change Summary
binaries/version.go	Updated PrismaVersion from "5.16.2" to "5.19.0" and EngineVersion from "34ace0eb2704183d2c05b60b52fba5c43c13f303" to "5fe21811a6ba0b952a3bc71400666511fe3b902f".
engine/request.go, engine/transform.go, engine/transform_test.go	Renamed transformResponse to TransformResponse and refactored it for structured JSON processing; updated test cases to reflect the new function name and improved coverage.
runtime/transaction/result.go	Added dependency on engine package to transform response data using TransformResponse in Get method.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant Engine

    User->>CLI: Run Prisma Command
    CLI->>Engine: Execute with Engine Version
    Engine-->>CLI: Return Results
    CLI-->>User: Display Results

Loading

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9a9e03a and 1c6b509.

Files selected for processing (5)

• binaries/version.go (1 hunks)
• engine/request.go (2 hunks)
• engine/transform.go (1 hunks)
• engine/transform_test.go (2 hunks)
• runtime/transaction/result.go (2 hunks)

Files skipped from review as they are similar to previous changes (1)

• binaries/version.go

Additional comments not posted (8)

runtime/transaction/result.go (1)

24-26: LGTM! Enhanced error handling.

The changes introduce an additional error check, ensuring that the data is correctly transformed before being used.

The code changes are approved.

engine/transform.go (2)

8-12: LGTM! Enhanced clarity and maintainability.

The introduction of the Input type enhances the clarity and maintainability of the code by explicitly defining the data format.

The code changes are approved.

---

14-42: LGTM! Improved JSON data handling.

The revised TransformResponse function handles JSON data in a more structured and clear manner, improving type safety and simplifying the logic.

The code changes are approved.

engine/transform_test.go (2)

6-6: LGTM! Improved test coverage and readability.

The use of assert.Equal enhances readability and simplifies the comparison.

The code changes are approved.

---

18-30: LGTM! Comprehensive test case.

The new test case introduces a more complex input structure and validates the transformation of a comprehensive dataset, ensuring that the TransformResponse function works as expected.

The code changes are approved.

engine/request.go (3)

51-53: LGTM!

The renaming of transformResponse to TransformResponse is appropriate for making the function public. The logic and control flow remain unchanged.

The code changes are approved.

---

72-74: LGTM!

The renaming of transformResponse to TransformResponse is appropriate for making the function public. The logic and control flow remain unchanged.

The code changes are approved.

---

51-53: Verify the definition of TransformResponse.

Ensure that the function TransformResponse is correctly defined and used in the codebase.

Run the following script to find the definition of TransformResponse:

#!/bin/bash
# Description: Verify the definition of `TransformResponse`.

# Test: Search for the function definition. Expect: Only one occurrence of the function definition.
ast-grep --lang go --pattern 'func TransformResponse($_) $_'

Also applies to: 72-74

Warning

Review ran into problems

Problems (1)

• Git: Failed to clone repository. Please contact CodeRabbit support.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.