Yiming Cao comments

Results 248 comments of


                                            Yiming Cao

Adding `@ignore` removes types (m-n relation) from the Kysely index file.

Hi @AliNectar , how is Kysely involved here? Are you using a prisma kysely generator?

Adding `@ignore` removes types (m-n relation) from the Kysely index file.

Have you checked if the generated Prisma schema is correct? The Kysely generator is run by the standard Prisma generate command.

Adding `@ignore` removes types (m-n relation) from the Kysely index file.

> There were no changes in the generated Prisma schema file. (only the expected change of adding [@ignore](https://github.com/ignore)). But note that we use supabase. And supabase implicitly creates tables for...

[Feature Request] A setting to disable the update pop-up in the VSCode extension

Hi @NatoBoram , this window is used to introduce major new features and it should only show up once. Do you find it appears repeatedly?

[BUG] - having delete and create in the same query starts first with create and only then with delete - ignoring the order if the object

Thanks for filing it. The bug is a nasty one: when enforcing access policies, we have to execute some nested operations separately, which effectively breaks the order. Please make multiple...

[Feature Request] REST API Handler: Optional relationship ids in response

Hi @zupamario , thanks for filing this. I think it makes sense to add it as an option to the RESTAPIHandler. Would you be interested in making a PR? I'll...

[Feature Request] Built-in Phone Validation

Related https://github.com/colinhacks/zod/issues/3378

[Bug] Prisma 6.6.0 - using "prisma-client" provider defaults to '@prisma/client'

Hi @zngly-vlad , the "prisma-client" generator is still in early access and completely untested with ZenStack yet.

[Bug] Prisma 6.6.0 - using "prisma-client" provider defaults to '@prisma/client'

Thank you! Appreciate it!

[Bug] Prisma 6.6.0 - using "prisma-client" provider defaults to '@prisma/client'

Hi @mhodgson , I appreciate your time researching the issue and sharing the findings. We'll evaluate it and will share thoughts back here soon!