chore: remove hardcoded URL validation and related tests#28297
Merged
Conversation
Since we won't have these attributes anymore in Prisma 7, as well as `env()` in the PSL, this validation is no longer possible. It's up to users to ensure that they don't hardcode any sensitive information in `prisma.config.ts`. Perhaps we could provide an ESLint plugin in the future to help with that. Ref: https://linear.app/prisma-company/issue/TML-1339/remove-url-directurl-shadowdatabaseurl-datasource-attributes-from-psl Ref: https://linear.app/prisma-company/issue/TML-1340/remove-env-from-psl
Contributor
size-limit report 📦
|
jkomyno
approved these changes
Oct 15, 2025
aqrln
added a commit
that referenced
this pull request
Nov 17, 2025
Since we won't have these attributes anymore in Prisma 7, as well as `env()` in the PSL, this validation is no longer possible. It's up to users to ensure that they don't hardcode any sensitive information in `prisma.config.ts`. Perhaps we could provide an ESLint plugin in the future to help with that. Ref: https://linear.app/prisma-company/issue/TML-1339/remove-url-directurl-shadowdatabaseurl-datasource-attributes-from-psl Ref: https://linear.app/prisma-company/issue/TML-1340/remove-env-from-psl
aqrln
added a commit
that referenced
this pull request
Nov 17, 2025
Since we won't have these attributes anymore in Prisma 7, as well as `env()` in the PSL, this validation is no longer possible. It's up to users to ensure that they don't hardcode any sensitive information in `prisma.config.ts`. Perhaps we could provide an ESLint plugin in the future to help with that. Ref: https://linear.app/prisma-company/issue/TML-1339/remove-url-directurl-shadowdatabaseurl-datasource-attributes-from-psl Ref: https://linear.app/prisma-company/issue/TML-1340/remove-env-from-psl
aqrln
added a commit
that referenced
this pull request
Nov 17, 2025
Since we won't have these attributes anymore in Prisma 7, as well as `env()` in the PSL, this validation is no longer possible. It's up to users to ensure that they don't hardcode any sensitive information in `prisma.config.ts`. Perhaps we could provide an ESLint plugin in the future to help with that. Ref: https://linear.app/prisma-company/issue/TML-1339/remove-url-directurl-shadowdatabaseurl-datasource-attributes-from-psl Ref: https://linear.app/prisma-company/issue/TML-1340/remove-env-from-psl
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.
Since we won't have these attributes anymore in Prisma 7, as well as
env()in the PSL, this validation is no longer possible.It's up to users to ensure that they don't hardcode any sensitive
information in
prisma.config.ts. Perhaps we could provide an ESLintplugin in the future to help with that.
Ref: https://linear.app/prisma-company/issue/TML-1339/remove-url-directurl-shadowdatabaseurl-datasource-attributes-from-psl
Ref: https://linear.app/prisma-company/issue/TML-1340/remove-env-from-psl