feat: update ppg for other dbs section #7264
Conversation
WalkthroughThe PR standardizes Prisma Postgres quickstarts (Kysely, Drizzle ORM, TypeORM, Prisma ORM) to a unified, ESM + strict-TypeScript flow: project bootstrapping, create-db CLI for ephemeral DB provisioning, .env-driven DATABASE_URL parsing into connection params with ssl, module-style .ts imports, sidebar navigation updates, redirect additions, and removal of one intro page. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20–25 minutes
Possibly related PRs
Pre-merge checks❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
Comment |
Dangerous URL checkNo absolute URLs to prisma.io/docs found. |
Redirect checkThis PR probably requires the following redirects to be added to static/_redirects: |
🍈 Lychee Link Check Report
📊 Results Overview
Errors per inputErrors in 200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/115-connection-pool.mdx
Errors in 200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx
Errors in 200-orm/200-prisma-client/500-deployment/650-caveats-when-deploying-to-aws-platforms.mdx
Errors in 800-guides/070-cloudflare-d1.mdx
Errors in 800-guides/090-nextjs.mdx
Errors in 800-guides/170-react-router-7.mdx
|
Deploying docs with
|
| Latest commit: |
14062e1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2fff0e04.docs-51g.pages.dev |
| Branch Preview URL: | https://dc-6216-other-dbs.docs-51g.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx (1)
165-203: Consider simplifying connection string handling.The manual URL parsing (lines 175-184) adds complexity that may not be necessary for a quickstart. The
pgPool acceptsconnectionStringdirectly and will handle SSL parameters from the query string (e.g.,?sslmode=require).Consider simplifying to:
const pool = new Pool({ connectionString: process.env.DATABASE_URL, ssl: { rejectUnauthorized: false } })This would make the quickstart more accessible while still being functionally correct.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx(2 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/300-typeorm.mdx(1 hunks)content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdx(8 hunks)content/250-postgres/100-introduction/225-import-from-existing-database.mdx(0 hunks)content/250-postgres/50-getting-started/200-import-from-existing-database.mdx(1 hunks)sidebars.ts(0 hunks)static/_redirects(1 hunks)
💤 Files with no reviewable changes (2)
- sidebars.ts
- content/250-postgres/100-introduction/225-import-from-existing-database.mdx
🧰 Additional context used
🧠 Learnings (6)
📓 Common learnings
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".
Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
📚 Learning: 2025-10-08T16:23:00.388Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".
Applied to files:
content/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/300-typeorm.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx
📚 Learning: 2025-10-09T21:32:50.340Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.
Applied to files:
content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdx
📚 Learning: 2025-10-08T16:22:57.129Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.
Applied to files:
content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx
📚 Learning: 2025-08-11T09:40:55.237Z
Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Applied to files:
content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdxcontent/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx
📚 Learning: 2025-10-08T16:23:00.388Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.
Applied to files:
content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx
⏰ 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). (2)
- GitHub Check: Check internal links
- GitHub Check: Cloudflare Pages
🔇 Additional comments (31)
content/100-getting-started/03-prisma-postgres/100-quickstart/300-typeorm.mdx (7)
1-8: Well-structured introduction and metadata.The frontmatter and introduction are clear and properly formatted with correct sentence case for the title and appropriate meta descriptions.
15-52: Excellent CLI-first setup approach.The progression from generating the TypeORM project via CLI, showing the generated structure, installing dependencies including dotenv, is clear and user-friendly. This standardized approach aligns well with the PR objectives.
54-111: Strong database setup and security practices.The
create-dbCLI integration is well-documented with realistic output, and the security warning against committing.envfiles is appropriately prominent. The reference to the create-db documentation and Prisma Data Platform claiming process adds helpful context.
113-159: Environment-driven configuration with proper security.The
parseConnectionStringfunction cleanly extracts connection parameters from the DATABASE_URL environment variable, andssl: trueis correctly set for Prisma Postgres. The use of dotenv/config and the spread operator for applying parsed parameters is idiomatic and appropriate.Minor observation: The non-null assertion on
process.env.DATABASE_URL!at line 138 assumes the variable is always present. For a quickstart this is acceptable, but in production code you'd want validation or a helpful error message if it's missing.
162-177: Clear execution instructions with expected output.The final steps guide users to run the application and show the expected console output. Note that the output references user insertion and loading operations—verify this matches what the default TypeORM generated project actually produces after running
npm start.
179-181: Helpful conclusion with external reference.The "Next steps" section appropriately directs users to TypeORM documentation for more advanced features, providing a natural learning progression.
12-13: Correct Node.js minimum version requirement.The documentation specifies Node.js 16+, but TypeORM's actual minimum is Node.js 14 or newer. The TypeScript 4.5+ requirement is accurate. Update the Node.js prerequisite to 14+ to match TypeORM's supported range and avoid unnecessarily restricting users on valid versions.
⛔ Skipped due to learnings
Learnt from: jy-joung-bitor Repo: prisma/docs PR: 0 File: :0-0 Timestamp: 2025-10-15T06:36:42.423Z Learning: The `tsc --init` command requires the `--types node` flag to properly include Node.js type definitions from `types/node` in the generated tsconfig.json, even when types/node is already installed. Without this flag, TypeScript may not automatically pick up Node.js typings.content/250-postgres/50-getting-started/200-import-from-existing-database.mdx (1)
11-11: LGTM!The redirect target update clarifies the destination path by explicitly mentioning "postgresql" instead of the generic path. This aligns with the PR's objective of standardizing Prisma Postgres documentation navigation.
content/100-getting-started/03-prisma-postgres/100-quickstart/50-prisma-orm.mdx (10)
19-21: LGTM!The project setup section uses a reusable component and follows the standardized approach across the quickstart guides.
23-37: LGTM!The dependency installation section clearly explains each package's purpose and properly separates development dependencies from runtime dependencies. The link to the node-postgres driver adapter documentation provides helpful context.
39-64: LGTM!The ESM configuration is properly set up with modern TypeScript settings. The
module: "ESNext"withmoduleResolution: "node"andtype: "module"in package.json ensures proper ESM support.
88-105: LGTM!Adding
dotenv/configto the Prisma config ensures environment variables are loaded before Prisma attempts to connect to the database. The configuration structure follows best practices.
107-118: LGTM!The generator configuration correctly uses the ESM-first
prisma-clientprovider with the custom output path that matches the--outputflag from the initialization command.
120-151: LGTM!The data model demonstrates a proper one-to-many relationship between User and Post with explicit foreign keys and relation fields. This is a good educational example for the quickstart.
153-167: LGTM!Explicitly showing both
prisma migrate devandprisma generateas separate steps helps users understand the migration and client generation workflow, even though migrate auto-generates the client.
169-231: LGTM!The Prisma Client instantiation properly uses the PrismaPg adapter with environment variable loading. The query examples demonstrate nested writes and includes, which are good teaching examples. Error handling with proper client disconnection is also present.
241-243: LGTM!The Studio exploration section uses a reusable component, maintaining consistency with the modular approach throughout the guide.
66-86: The perceived inconsistency is actually intentional and correct—no action needed.The review identifies a real surface-level difference: the Prisma ORM guide uses
npx prisma init --dbwhile Kysely, Drizzle, and TypeORM all usenpx create-db. However, this difference reflects a deliberate design choice, not a bug.Here's why each approach is correct:
Prisma ORM needs
prisma init --dbbecause it must initialize the entire Prisma project structure (creatingschema.prisma, setting up Prisma Client, etc.) and provision the database in one step.Kysely, Drizzle, and TypeORM use
npx create-dbbecause they're third-party ORMs that don't require Prisma project initialization. They only need the database provisioned; they'll connect to it with their own configuration.This isn't an inconsistency requiring standardization—it's the correct pattern for each framework's setup needs. The Prisma ORM guide is a complete project bootstrap, while the others are standalone database provisioning steps.
Likely an incorrect or invalid review comment.
content/100-getting-started/03-prisma-postgres/100-quickstart/100-kysely.mdx (7)
10-31: LGTM!The prerequisites clearly state the strict mode requirement for Kysely's type safety, which is important context. The manual project setup provides more transparency than a component abstraction.
33-69: LGTM!The TypeScript configuration properly sets up strict mode with a clear note emphasizing its requirement for Kysely. The
allowImportingTsExtensionsandnoEmitoptions are appropriate for a TypeScript-only execution environment using tsx.
71-129: LGTM!The create-db CLI workflow is clearly documented with realistic output examples. The warnings about securing credentials and the claim process for temporary databases provide important context for users.
131-145: LGTM!The dependency installation section clearly explains each package's role and properly separates development dependencies from runtime dependencies.
147-163: LGTM!The database type definitions properly use Kysely's
Generatedtype for auto-incrementing IDs and correctly represent nullable fields. This demonstrates Kysely's type-safe approach well.
205-265: LGTM!The query examples provide a good progression from schema creation through data insertion to querying. The use of
ifNotExists()makes the script idempotent, and the example output helps users verify their setup.
267-269: LGTM!The closing section provides a clear path forward to more advanced Kysely features.
content/100-getting-started/03-prisma-postgres/100-quickstart/200-drizzle-orm.mdx (5)
10-42: LGTM!The prerequisites and project setup follow the same transparent, manual approach as the Kysely guide, which helps users understand each step of the setup process.
44-101: LGTM!The database creation workflow is consistent with the Kysely guide and provides clear instructions with realistic CLI output examples and appropriate security warnings.
103-119: LGTM!The dependency installation section is clear and includes
drizzle-kitfor migration tooling, which is important for a complete Drizzle ORM setup. The package breakdown is helpful.
121-184: LGTM!The query execution section demonstrates a simple connection test with proper error handling. The detailed output example (lines 158-184) is educational, showing the full PostgreSQL
Resultobject structure, though users might find it verbose for a quickstart.
186-188: LGTM!The closing section provides a clear path forward to more advanced Drizzle ORM features.
static/_redirects (1)
824-824: No duplicate redirect rules detected—the review comment concern is invalid.Verification confirms that line 824 is the sole entry for
/postgres/introduction/import-from-existing-database*in the redirects file. The original AI summary suggesting duplicated mappings was inaccurate. The redirect rule is correctly formed and stands alone with no conflicts.
🍈 Lychee Link Check Report
📊 Results Overview
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/css/custom.css (1)
1832-1838: CSS styling looks good; consider clarifying selector specificity.The CSS rules correctly apply normal font weight and size to category labels with the
sidebar-item-normal-weightclass, matching the sidebar changes. The use of!importantis appropriate to override the existing bold category label styles (line 127).The second selector (line 1834) uses a descendant combinator, which will match any nested element with the class, not just immediate children. Given the current usage in
sidebars.tswhere the class is directly on the category, this works fine. However, if you want to be more explicit:Consider using a child combinator for clarity:
/* Make category labels with normal weight class have normal font weight and size */ .theme-doc-sidebar-item-category.sidebar-item-normal-weight > .menu__list-item-collapsible > .menu__link, -.theme-doc-sidebar-item-category .sidebar-item-normal-weight > .menu__list-item-collapsible > .menu__link { +.theme-doc-sidebar-item-category > .sidebar-item-normal-weight > .menu__list-item-collapsible > .menu__link { font-weight: normal !important; font-size: 14px !important; line-height: 1.25 !important; }This change makes the selector more restrictive and the intent clearer, though it's not strictly necessary given the current usage.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (18)
content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx(0 hunks)content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdx(0 hunks)content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx(0 hunks)sidebars.ts(1 hunks)src/css/custom.css(1 hunks)
💤 Files with no reviewable changes (16)
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/100-prisma-postgres.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/200-sqlite.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/400-mysql.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/800-mongodb.mdx
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/800-mongodb.mdx
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/400-mysql.mdx
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/200-sqlite.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/300-postgresql.mdx
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/600-planetscale.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/600-planetscale.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/500-sql-server.mdx
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/500-sql-server.mdx
- content/100-getting-started/02-prisma-orm/100-quickstart/700-cockroachdb.mdx
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/700-cockroachdb.mdx
- content/100-getting-started/02-prisma-orm/200-add-to-existing-project/300-postgresql.mdx
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.
Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".
📚 Learning: 2025-10-08T16:22:57.129Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.
Applied to files:
sidebars.ts
📚 Learning: 2025-10-08T16:23:00.388Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.
Applied to files:
sidebars.ts
📚 Learning: 2025-10-08T16:23:00.388Z
Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".
Applied to files:
sidebars.ts
⏰ 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). (2)
- GitHub Check: Check internal links
- GitHub Check: Cloudflare Pages
🔇 Additional comments (1)
sidebars.ts (1)
211-233: LGTM! Clear grouping of alternative tools.The nested category structure is well-formed and correctly groups Kysely, Drizzle ORM, and TypeORM under "Other tools". The
sidebar-item-normal-weightclassName properly connects to the CSS styling being added incustom.css.Note: The category is set to always be expanded (
collapsed: false, collapsible: false). This ensures visibility but removes user control over collapsing this section. If this is intentional to highlight these tools, it's a good choice.
* feat: add kysley * feat: add drizzle * feat: add typeorm * fix: clean-up * feat: separate the sections better * fix: remove badges
Summary by CodeRabbit
Documentation
Style