Skip to content

Conversation

@shahriar-shojib
Copy link

What does this PR do?

The casing for import from prisma was wrong, now it's correct.

The casing for import from prisma was wrong, now it's correct.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 24, 2025

Walkthrough

Updates symbol naming in Prisma adapter documentation from PrismaLibSQL to PrismaLibSql, affecting both the import statement and constructor call in code examples.

Changes

Cohort / File(s) Summary
Prisma Documentation Symbol Update
docs/guides/ecosystem/prisma.mdx
Updated import symbol from PrismaLibSQL to PrismaLibSql and corrected constructor call from new PrismaLibSQL(...) to new PrismaLibSql(...) in code sample

Pre-merge checks

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request description is incomplete. While it addresses 'What does this PR do?', the required 'How did you verify your code works?' section is entirely missing. Add the 'How did you verify your code works?' section to document testing or verification steps taken for the import case correction.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: correcting the import case for PrismaLibSql adapter, which matches the file modifications shown in the summary.

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.

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

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7906703 and 5ac79bd.

📒 Files selected for processing (1)
  • docs/guides/ecosystem/prisma.mdx
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: cirospaciari
Repo: oven-sh/bun PR: 22946
File: test/js/sql/sql.test.ts:195-202
Timestamp: 2025-09-25T22:07:13.851Z
Learning: PR oven-sh/bun#22946: JSON/JSONB result parsing updates (e.g., returning parsed arrays instead of legacy strings) are out of scope for this PR; tests keep current expectations with a TODO. Handle parsing fixes in a separate PR.
Learnt from: AmanVarshney01
Repo: oven-sh/bun PR: 23580
File: docs/guides/ecosystem/prisma.md:21-26
Timestamp: 2025-10-15T04:01:16.478Z
Learning: For Prisma with Bun runtime and Rust-free client (engineType "client"), when using local SQLite files (file:// URLs), use either prisma/adapter-better-sqlite3 or the Bun-native synapsenwerkstatt/prisma-bun-sqlite-adapter. The prisma/adapter-libsql adapter is only for remote libSQL/Turso endpoints and will not work with local SQLite file URLs.
📚 Learning: 2025-10-15T04:01:16.478Z
Learnt from: AmanVarshney01
Repo: oven-sh/bun PR: 23580
File: docs/guides/ecosystem/prisma.md:21-26
Timestamp: 2025-10-15T04:01:16.478Z
Learning: For Prisma with Bun runtime and Rust-free client (engineType "client"), when using local SQLite files (file:// URLs), use either prisma/adapter-better-sqlite3 or the Bun-native synapsenwerkstatt/prisma-bun-sqlite-adapter. The prisma/adapter-libsql adapter is only for remote libSQL/Turso endpoints and will not work with local SQLite file URLs.

Applied to files:

  • docs/guides/ecosystem/prisma.mdx

Comment on lines +105 to +107
import { PrismaLibSql } from "@prisma/adapter-libsql";

const adapter = new PrismaLibSQL({ url: process.env.DATABASE_URL || "" });
const adapter = new PrismaLibSql({ url: process.env.DATABASE_URL || "" });
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

@prisma/adapter-libsql PrismaLibSql export class name

💡 Result:

The exported class name is PrismaLibSQL (capital "SQL"). [1][2]

Sources:
[1] npm package readme for @prisma/adapter-libsql.
[2] Prisma docs — Database drivers (example using PrismaLibSQL).


Revert the casing change — PrismaLibSQL is the correct export name.

The export from @prisma/adapter-libsql is PrismaLibSQL (with capital "SQL"), not PrismaLibSql. Lines 105 and 107 should use PrismaLibSQL to match the actual package export. This change introduces broken code that won't work in practice.

🤖 Prompt for AI Agents
In docs/guides/ecosystem/prisma.mdx around lines 105 to 107, the import and
usage use the wrong casing "PrismaLibSql"; update both the import and the
instantiation to the correct exported identifier "PrismaLibSQL" to match
@prisma/adapter-libsql's actual export so the example compiles and runs.

@shahriar-shojib
Copy link
Author

https://www.npmjs.com/package/@prisma/adapter-libsql according to the latest package, the casing seems to be PrismaLibSql not PrismaLibSQL
However, on the Prisma docs, it is also wrong!

See this declaration:
https://unpkg.com/@prisma/adapter-libsql@7.2.0/dist/index-node.d.ts

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