Prisma-client-js: Remove compatibility plural api
In order to ease the transition, Prisma Client right now ships with a note with the old plural api, that it's deprecated.
We should by now remove the note, as it gets in the way with the autocompletion.
timsuchanek
All 2 comments
Any reason why this is removed? It reads weirdly
// This reads weird
馃ぎ const blogs = await prisma.blog.findMany()
// This reads greatly
馃槏 const blogs = await prisma.blogs.findMany()
deadcoder0904
on 29 Feb 2020
You refer to the old "pluralized API", not the "compatibility plural api" we had for a few versions that @timsuchanek mentioned above.
About the pluralized API:
The problem is if people already have pluralized table names like posts it created something like postes - which is _really_ awkward to use and non intuitive. Same problem in other, non English languages. Also if the table names for example use both way mixed at the same time. So for now we removed the feature. If you want to, you can use @map in your schema.prisma to rename the model (blog => blogs) which will also be reflects in Prisma Client.
We will think about how we can improve this experience in the future - we agree with your initial statement, but have to find a better way to offer that.
janpio
on 29 Feb 2020
Related issues
williamluke4
路
3Comments
nikolasburk
路
3Comments
divyenduz
路
4Comments
Errorname
路
3Comments
FluorescentHallucinogen
路
3Comments
Most helpful comment
You refer to the old "pluralized API", not the "compatibility plural api" we had for a few versions that @timsuchanek mentioned above.
About the pluralized API:
The problem is if people already have pluralized table names like
postsit created something likepostes- which is _really_ awkward to use and non intuitive. Same problem in other, non English languages. Also if the table names for example use both way mixed at the same time. So for now we removed the feature. If you want to, you can use@mapin yourschema.prismato rename the model (blog=>blogs) which will also be reflects in Prisma Client.We will think about how we can improve this experience in the future - we agree with your initial statement, but have to find a better way to offer that.