chrishoermann

@gascenciom1998 @odysseaspapadimas I'll look into it. the generator currently uses `@prisma/internals": "^4.13.0` and `@prisma/generator-helper": "^4.13.0`. I'll update to the latest versions and see if I can reproduce the error

in the latest version I updated the relevant prisma packages to `4.15`, tested it with my schema and was able to compile it. Can you please test your setup with...

@gascenciom1998 I did some digging and in your case this seems to actually be a model naming issue. I think that `List` in a model name can somehow lead to...

@amirhhashemi I can look into this but I currently can't give you a timeframe when I can implement this.

@oceandrama thanks for the hint. I need to look into this in more detail but I think it is because the omitted fields are currently only propagated to the "normal"...

@cimchd this seems like a cool addition but I don't really have experience with i18n or the package you mentiond so I need to dig into your link a bit....

I thought about this too but didn't take the time yet. But it is definitly on my todo list for the version that I'm currently working on that will also...

@MichaelOren Thanks for looking into this. I haven't used github actions yet but can you specify the issues a bit? I personally would like to stick with `pnpm`.

@oceandrama I chose to add the `Type` because if somehow you need to import the enum from `prisma client` it would be named `Role`. So to be able to distiguish...

@jafri that's interesting. Can you check if the uppercase type that should be used also exists somewhere in your `index.d.ts`? We had a similar bug where the name of a...