You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zenstack version 2.8.0 changed the type signature for nested creates/connects on delegates, incorrectly requiring referenced identifiers.
With the following schema:
model A {
id Int @id @default(autoincrement())
b B[]
}
model B {
id Int @id @default(autoincrement())
a A @relation(fields: [aId], references: [id])
aId Int
type String
@@delegate(type)
}
model C extends B {
f String?
}
But as of version 2.8.0, Zenstack defines the data signature (in the generated .logical-prisma-client/runtime/index-fixed.d.ts) as the following (requiring the aId reference property):
export type CCreateInput = {
aId: number
f?: string | null
a: ACreateNestedOneWithoutDelegate_aux_A_b_CInput
};
In previous versions, Zenstack defined it as expected:
Zenstack version 2.8.0 changed the type signature for nested creates/connects on delegates, incorrectly requiring referenced identifiers.
With the following schema:
I expect to be able to call something like:
But as of version 2.8.0, Zenstack defines the data signature (in the generated
.logical-prisma-client/runtime/index-fixed.d.ts
) as the following (requiring the aId reference property):In previous versions, Zenstack defined it as expected:
Environment:
The text was updated successfully, but these errors were encountered: