-
Support the below schema:
```prisma
model User {
id Int @id @default(autoincrement())
// posts Post[]. no need to specify it in Zmodel, ZenStack will generate it in the schema.prism…
-
We encounterd a bug when using generated prisma types with versions greater than `3.21.1`.
You can reproduce the issue in the following repo: https://github.com/chrishoermann/zod-prisma-types-bug…
-
**Description and expected behavior**
Hello again,
For a typical prisma schema, when you are doing a nested create of a related object, you don't need to specify the key of the record from which…
-
**Description and expected behavior**
The upsert operation on multiple nested relations is applied only to the last relation. Works fine with pure PrismaClient.
**Environment (please complete the …
-
### Background
There are some issues around our database querying. The primary issue is the complete omission of any access policy enforcement for some routes, which is obviously unacceptable. Secondl…
-
Getting the following error when using oslo with vite
![](https://github.com/pilcrowOnPaper/oslo/assets/31737273/0af1c0eb-3602-4537-804e-f11eb8ffbfef)
-
**Description and expected behavior**
I'm trying to use `@regex('^[0-9a-z\-]*$')` for slugs in my model, but the generated zod schema, which I'm using in a form, has a pattern like `new RegExp("^[0-9…
-
Hello! I guess it's more of a question: is there a reason for all model properties to be optional? I just upgraded to 1.5.0 from 1.2.0 and it broke a few types. I filed it as a bug since already optio…
-
## Basic Information
Currently, implementing a way to retrieve only a sufficient amount of data for a given user role in an API will result in a lot of code duplication and unmaintainable code.
F…
-
**Description and expected behavior**
I am having trouble setting this up and im not exactly sure what this error means.
I get this when I access `/api/model/users/2`
![image](https://github.com/z…