Prisma format adds invalid fragments to schema if composites are present on a model

[dpetrick]

Saving the following datamodel:

datasource db {
  provider = "mongodb"
  url      = "mongodb://prisma:prisma@127.0.0.1:27017/test?authSource=admin"
}

generator js {
  previewFeatures = ["mongodb"]
  provider        = "prisma-client-js"
}

model A {
  id String  @id @default(dbgenerated()) @map("_id") @db.ObjectId
  b  B
  c  C[]
}

type B {
  b_1 String
  b_2 Int
}

type C {
  c_1 Int
}

Results in the formatter rendering the datamodel like this:

datasource db {
  provider = "mongodb"
  url      = "mongodb://prisma:prisma@127.0.0.1:27017/testdb2?authSource=admin"
}

generator js {
  previewFeatures = ["mongodb"]
  provider        = "prisma-client-js"
}

model A {
  id String @id @default(dbgenerated()) @map("_id") @db.ObjectId
  b  B
  c  C[]
     // Note these two. The identation is also off, suggesting it doesn't find a suitable field name.
     B? 
     C?
}

type B {
  b_1 String
  b_2 Int
}

type C {
  c_1 Int
}

[pimeys]

Can confirm. It sucks.

[janpio]

Can confirm that 3.8.0-dev.47 does not show the behavior from above any more.