Skip to content

Conversation

@AmanVarshney01
Copy link
Member

@AmanVarshney01 AmanVarshney01 commented Dec 11, 2025

Summary by CodeRabbit

  • Documentation
    • Updated documentation to clarify that case-insensitive filtering for JSON fields is supported since version 6.4.0, enabling case-insensitive string filtering operations on JSON data.

✏️ Tip: You can customize this high-level summary in your review settings.

@github-actions
Copy link
Contributor

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 11, 2025

Walkthrough

This pull request updates the Prisma documentation to clarify that case-insensitive filtering for JSON fields is now supported as of version 6.4.0. The change corrects prior guidance by enabling mode: 'insensitive' for string-based filters on JSON data.

Changes

Cohort / File(s) Summary
JSON field filtering documentation
content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx
Updated documentation to reflect that case-insensitive filtering is supported for JSON fields starting from version 6.4.0, enabling mode: 'insensitive' in string filters such as string_contains, string_starts_with, and string_ends_with

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

  • Verify the version claim (6.4.0) is accurate against the actual Prisma changelog and release notes
  • Confirm that the stated filters (string_contains, string_starts_with, string_ends_with) correctly support the mode: 'insensitive' option for JSON fields
  • Ensure the documentation change doesn't contradict any other sections in the docs that may reference JSON filtering behavior

Pre-merge checks

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating documentation to reflect that case-insensitive filtering for JSON fields is now supported in Prisma version 6.4.0, replacing outdated information.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37f240c and 650b198.

📒 Files selected for processing (1)
  • content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Check internal links
🔇 Additional comments (1)
content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx (1)

1055-1058: Verify that version 6.4.0 is the correct release for this feature.

The FAQ answer is clear and well-structured, and it properly aligns with the examples shown earlier in the document (lines 264–297), which already demonstrate the mode: 'insensitive' option in action. The reference to the "Filter on object property" section is appropriate and helpful.

However, please confirm that version 6.4.0 is the accurate release in which this feature was introduced. You can verify this against the official Prisma release notes or changelog.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Contributor

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

  • This PR does not change any pages in a way that would require a redirect.

@github-actions
Copy link
Contributor

🍈 Lychee Link Check Report

Note: Links are cached for 5 minutes. Failed links (timeouts, rate limits) are retried in a second run with longer timeout.

📊 Results Overview

Status Count
🔍 Total 2292
✅ Successful 2261
⏳ Timeouts 0
🔀 Redirected 4
👻 Excluded 24
❓ Unknown 0
🚫 Errors 2
⛔ Unsupported 1

Errors per input

Errors in 200-orm/050-overview/500-databases/840-cockroachdb.mdx

Errors in 800-guides/320-permit-io-access-control.mdx

@cloudflare-workers-and-pages
Copy link

Deploying docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 650b198
Status: ✅  Deploy successful!
Preview URL: https://387543e3.docs-51g.pages.dev
Branch Preview URL: https://case-sensitive-json.docs-51g.pages.dev

View logs

@AmanVarshney01 AmanVarshney01 merged commit 19d27fa into main Dec 11, 2025
7 of 8 checks passed
@AmanVarshney01 AmanVarshney01 deleted the case-sensitive-json branch December 11, 2025 18:53
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.

3 participants