Fix misleading error when db.url
is undefined
#8696
Merged
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.
When
config.db.url
wasundefined
- although not allowed by our types - users were faced with the following error:This can happen if, for example, someone used
db.url: process.env.DATABASE_URL!
.You shouldn't do this, but, the error doesn't need to be terrible, when the alternative is that Prisma will inform you that your connection url is empty.
Some day, we should use something like
zod
to validate a users configuration.