Conversation
…happens (#49) We can't check Prisma's error type against PrismaClientKnownError class because we can't reference generated Prisma classes from the internal package. Use a weakly-typed checking instead.
- following Prisma's logging paradigm, make logging configuration with several levels to stdout or event emitting - moving some logic from generated code to the DefaultService abstract base class in runtime
use extra typing information for back and forth serialization
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ymc9
added a commit
that referenced
this pull request
Nov 9, 2022
ymc9
added a commit
that referenced
this pull request
Feb 10, 2026
* fix: several issues with ts schema generation * addressing review comments
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
1 participant
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 #48 #54 #45 #53 #51 #58