thread '<unnamed>' panicked at 'Every RelationInfo should have a complementary RelationInfo on the opposite relation field.'

prisma validate/format crash on this schema:

datasource db {
  provider = "sqlserver"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model Test {
  id         Int        @id
  fk         Int
  testparent TestParent @relation(fields: [fk], references: [id])
}

model TestParent {
  id    Int    @id
  tests Test[]

  fk   Int
  self TestParent @relation(fields: [fk], references: [id])
}

with:

thread '<unnamed>' panicked at 'Every RelationInfo should have a complementary RelationInfo on the opposite relation field.', libs\datamodel\connectors\dml\src\datamodel.rs:165:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Unexpected token E in JSON at position 0

This is surprising, as usually the missing backrelation validation works fine, e.g. when you only have the second model without the relation to the first one:

model TestParent {
  id    Int    @id
  fk   Int
  self TestParent @relation(fields: [fk], references: [id])
}

[ChipClark]

Confirmed fixed in v3.2.1

FYI - this is in production with NestJS 7.6.0

[janpio]

Can you please confirm this is also fixed for you with 3.2.x @ChipClark?