Internal: reformatter is not idempotent #12726
Labels
bug/2-confirmed
Bug has been reproduced and confirmed.
kind/bug
A reported bug.
team/schema
Issue for team Schema.
tech/engines/datamodel
Issue about parsing/validation/rendering of the Prisma schema
tech/engines
Issue for tech Engines.
topic: internal
topic: prisma format
CLI: prisma format
Milestone
The problem is the ordering of the attributes on
bazId
. The first reformatter run adds an@unique
attribute because it's a 1:1 relation. Due to the way the reformatter is implemented, that attribute lands at the end of the list. The second run applies the expected ordering for attributes, putting@unique
before@db.ObjectId
.related: #12580
The text was updated successfully, but these errors were encountered: