Bug description
In most cases, Prisma generate DMMF type names with a proper PascalCase names:
However, in some cases (for now I found only CreateOrConnectWithout) it uses the field name directly, without converting to PascalCase:
How to reproduce
Expected behavior
I would expect consistent type names to be always PascalCase.
Prisma information
Environment & setup
- OS: Windows 10 @ WSL 2 (Ubuntu 20.04)
- Database:
- Node.js version: v15.3.0
- Prisma version:
@prisma/cli : 2.15.0
@prisma/client : 2.15.0
Current platform : debian-openssl-1.1.x
Query Engine : query-engine e51dc3b5a9ee790a07104bec1c9477d51740fe54 (at node_modules/@prisma/engines/query-engine-debian-openssl-1.1.x)
Migration Engine : migration-engine-cli e51dc3b5a9ee790a07104bec1c9477d51740fe54 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine : introspection-core e51dc3b5a9ee790a07104bec1c9477d51740fe54 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary : prisma-fmt e51dc3b5a9ee790a07104bec1c9477d51740fe54 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Studio : 0.340.0
Bug description
In most cases, Prisma generate DMMF type names with a proper PascalCase names:
However, in some cases (for now I found only
CreateOrConnectWithout) it uses the field name directly, without converting to PascalCase:How to reproduce
Expected behavior
I would expect consistent type names to be always PascalCase.
Prisma information
Environment & setup