Skip to content
This repository was archived by the owner on Jan 14, 2021. It is now read-only.
This repository was archived by the owner on Jan 14, 2021. It is now read-only.

Adapt a more conflict resistant naming for Prisma client's types #707

@pantharshit00

Description

@pantharshit00

Right now properties like ${name}Client are ending up in the denyList and it is very common to name something like UserClient.

This adds unnecessary friction and we can totally avoid this by using a more conflict resistant naming for types like User__Client.

Internal: https://prisma-company.slack.com/archives/CUXLS0Z6K/p1590736839231000

Related: prisma/prisma#2539

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/improvementAn improvement to existing feature and code.tech/typescriptIssue for tech TypeScript.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions