-
Notifications
You must be signed in to change notification settings - Fork 49
Open
Description
Problem
The VSCode extension does not support a custom path for prisma.config.ts
Suggested solution
Add support for specifying a custom path for prisma.config.ts in the VSCode extension, similar to how prisma.schemaPath
is handled.
"prisma.configPath": {
"type": "string",
"examples": [
"/path/to/your/prisma.config.ts"
],
"description": "If you have a prisma config file in a custom path, you will need to provide the path, e.g., `/path/to/your/prisma.config.ts`."
}
Alternatives
It is still possible to continue using prisma.schemaPath
as it currently exists.
Metadata
Metadata
Assignees
Labels
No labels