Formatter doesn't allow comments on consecutive indices

[lostfictions]

Bug description

In a model with multiple indices declared with @@index, the Prisma formatter will move the indices to be on consecutive lines, even if there are comments between them.

How to reproduce

Use this schema:

model Trigram {
  first   String
  second  String
  third   String
  count   Int    @default(0)

  // index for forward access.
  @@index([channel, first, second])
  // index for reverse access.
  @@index([channel, third, second])
}

Run prisma format. The schema will be formatted as follows:

model Trigram {
  first   String
  second  String
  third   String
  count   Int    @default(0)

  // index for forward access.
  // index for reverse access.
  @@index([channel, first, second])
  @@index([channel, third, second])
}

Expected behavior

Comments in between consecutive @@index statements are not reordered.

Prisma information

Environment & setup

• OS: Linux
• Database: N/A
• Node.js version: 17.4.0

Prisma Version

prisma                  : 3.8.1
@prisma/client          : 3.8.1
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine        : migration-engine-cli 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine    : introspection-core 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary           : prisma-fmt 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash    : 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f
Studio                  : 0.452.0

[janpio]

Can confirm with this model:

model Trigram {
  id      Int @id
  first   String
  second  String
  third   String
  count   Int    @default(0)

  // index for forward access.
  @@index([count, first, second])
  // index for reverse access.
  @@index([count, third, second])
}

Is reformatted to

model Trigram {
  id     Int    @id
  first  String
  second String
  third  String
  count  Int    @default(0)

  // index for forward access.
  // index for reverse access.
  @@index([count, first, second])
  @@index([count, third, second])
}

[tomhoule]

The schema above now reformats to:

model Trigram {
  first  String
  second String
  third  String
  count  Int    @default(0)

  // index for forward access.
  @@index([channel, first, second])
  // index for reverse access.
  @@index([channel, third, second])
}

that was fixed in prisma/prisma-engines#3030. So I think we can close this issue, thanks for reporting the problem!