Fix: Correctly locate migrations folder for multi-file Prisma schema #21
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.
Summary
Fixes the bug where migrations were created in the wrong location when using multi-file Prisma schema configuration (issue #20).
Problem
When using
--schemapointing to a folder (multi-file schema), the generator was creating migrations in./schema/migrations/instead of the correct location at the same level as the schema folder.Root cause: The code was using
path.dirname(schemaPath)which pointed to the schema folder itself, not its parent directory.Solution
config.outputDir(already correctly resolved by Prisma) instead ofpath.dirname(schemaPath)schemaPathvariable from generate functionbaseDirPathparameter tomigrationsDirfor better clarityChanges
config.outputDirfor migration base pathexecuteGeneratehelper to handle multi-file schemagetMigrationsDirhelper to handle multi-file schemaTest Results
✅ All 55 tests passing
✅ New test case for multi-file schema configuration
✅ Backward compatible - single-file schema behavior unchanged
Test plan
Fixes #20