docs(backend): document prisma.config.ts and its role alongside schema.prisma - #1146
Open
Fury03 wants to merge 1 commit into
Open
docs(backend): document prisma.config.ts and its role alongside schema.prisma#1146Fury03 wants to merge 1 commit into
Fury03 wants to merge 1 commit into
Conversation
Contributor
Author
Note on the failing CI checksThe red checks here are pre-existing on
This PR changes only Markdown, so it cannot affect any of those jobs — a docs edit does not change Happy to open a separate PR fixing the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1095
Problem
backend/prisma.config.tsconfigures the Prisma CLI (schema path, migrations path, datasource URL) separately from the data model inbackend/prisma/schema.prisma, but neitherbackend/README.mdnordocs/DEVELOPMENT.mdmentioned the file. A contributor debugging aprisma generate/prisma migratequirk had no pointer to check it.Changes
backend/README.md— new subsection under Prisma Database:schema.prismaowns the data model,prisma.config.tsowns CLI configuration..envfor CLI commands, which is why the file opens withimport "dotenv/config".schema,migrations.path,datasource.url).DATABASE_URL, paths resolving relative tobackend/, and the seed command still living in the legacyprisma.seedfield ofpackage.jsonrather thanmigrations.seedin the config.docs/DEVELOPMENT.md— two links into that section:prisma:generate/prisma:migratecommands.Out of scope
No changes to the Prisma config itself, and no migration to a different config format — docs only.