VSCode: Better way to create relations

[janpio]

Problem

The relations syntax of Prisma is quite involved: https://www.prisma.io/docs/concepts/components/prisma-schema/relations

To go from

model User {
  id      Int      @id @default(autoincrement())
}

model Post {
  id         Int         @id @default(autoincrement())
  authorId   Int
}

to

model User {
  id      Int      @id @default(autoincrement())
  posts   Post[]
}

model Post {
  id         Int         @id @default(autoincrement())
  authorId   Int
  author     User        @relation(fields: [authorId], references: [id])
}

or alternatively to create something like

model User {
  id             Int     @default(autoincrement()) @id
  name           String?
  successorId Int?
  successor   User?   @relation("BlogOwnerHistory", fields: [successorId], references: [id])
  predecessor User?   @relation("BlogOwnerHistory")
}

you need to

1. know and type a new field with a model type
2. know and type @relation
3. know any type fields and know that its value has to point to the relation scalar field (= FK field)
4. know and type references and know that its value has to reference the other, referenced field
5. optionally also know when the @relation needs to be named for disambiguation

Suggested Solution

It would be amazing if the Prisma VSCode extension could help me create the relation between to models.

• I could select to models, then define which one should link to the other, select the relation scalar and be lead through the further decisions - and the code is generated.
• Or I could select the relation scalar, and then be lead through the decisions to set up the relation - and the code is generated.

It is unclear to me what that would look like in VSCode, what UI is appropriate in that context.

[Druue]

It is unclear to me what that would look like in VSCode, what UI is appropriate in that context.

This to me seems like code-actions or refactorings would be appropriate.

Currently there is very limited interactivity available. There is the option to move the user cursor around to effectively prompt the user to type in what they want but it's not quite as advanced as what you describe.

If I understand correctly, it seems the following issue is more in line: LSP#1579, in which case, this is pending upstream changes