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.
special pr for eric
Here is a summary of the work I've done:
To address the breaking changes introduced in Prisma v6.6.0+, I've made several updates to the
prismaExtension
to ensure its compatibility and improve its functionality:usingSchemaFolder
detection and thetypedSql
preview feature to make the extension more robust and easier to maintain.copy
option: You can now disable the automatic copying of the Prisma schema and migrations to the output directory by setting thecopy
option tofalse
.prisma
directory in the output path. Instead, the Prisma client is generated in the root of the output directory, which aligns with the new behavior of Prisma 6.6.0+.copy
option and the necessarypackage.json
configuration for Prisma 6.6.0+.Overall, these changes should resolve the issues you were seeing and make the
prismaExtension
more flexible and easier to use. Let me know if you have any other questions!