latest versions are not published to npm

[terion-name]

npm packages are outdated. e.g.: https://www.npmjs.com/package/@paljs/generator — 4.0.12 https://www.npmjs.com/package/@paljs/plugins — 4.0.8

[terion-name]

@AhmedElywa pleeeeease publish latest versions to npm

[AhmedElywa]

I was out last three days I have an error in building I will fix it when i back You can expect to have the new release tomorrow morning EU Time

[terion-name]

@AhmedElywa thank you!

[terion-name]

@AhmedElywa pleeeeease 🙏

[AhmedElywa]

@terion-name sent the last version 4.0.13 with the last prisma version 3.6.0 why you need it no change happen

[terion-name]

@AhmedElywa we've updated to prisma 3.6.0 recently in one of my apps in develop. And we've discovered that generateInputsString, even without any filters and postprocessing, missing some inputs that are required by prisma. Thought it was some mismatch in prisma engine and generator versions (don't know if it was there prior, updating deps or rolling back in this case is a huge pain).

Session model has many Acts Act has one Document

Act model:

model Act {
  id String @id @default(cuid())

  session Session @relation(name: "ActSession", fields: [sessionId], references: [id])
  sessionId String

  document DocumentsDocument @relation(name: "ActDocumentsDocument", fields: [docId], references: [id])
  docId String

  accepted Boolean @default(false)
  isManual Boolean @default(false)

  votes Vote[] @relation(name:"VoteAct")

  createdAt DateTime @default(now())
  updatedAt DateTime @default(now())
}

in updateSession mutation in SessionUpdateInput there is acts → createOrConnect → create (of type ActUncheckedCreateWithoutSessionInput) that has no document field:

But it is required there by Prisma (should be something like DocumentUncheckedCreateNestedWithoutArticleInput):

Argument document for data.acts.connectOrCreate.0.create.document is missing.

Meanwhile acts → create is fine and has document field

[AhmedElywa]

did the new release fixed the issue or still there I already have the same issue for my app

[terion-name]

@AhmedElywa nope, after update inputs are the same (

[terion-name]

@AhmedElywa it seems that it is on prisma's side :(

https://github.com/prisma/prisma/issues/9989