Code completion issue

Hi, currently the auto formatting in VSCode gives me PascalCase entity relations but according to the docs this is kind of an anti-pattern.

I’m also very sure that this was not the case just a while ago. Not sure when exactly this changed. Is this a bug or did the convention actually change recently?

I’m on Prisma Extension 2.6.0 and I’m using prisma cli and client in version 2.6.0 as well.

Input:

model TestModel {
  id String @id @default(cuid())
  testModel OtherTestModel
}

model OtherTestModel {
  id String @id @default(cuid())
}

Output after save:

model TestModel {
  id               String         @id @default(cuid())
  testModel        OtherTestModel @relation(fields: [otherTestModelId], references: [id])
  otherTestModelId String
}

model OtherTestModel {
  id        String      @id @default(cuid())
  TestModel TestModel[] // <- this should be camelCase?!
}

[jsbrain]

Alright @janpio, thank you for your investigation, I’m going to do as you advise 😇

[janpio]

That version is from December last year, https://github.com/prisma/prisma/releases/tag/2.0.0-preview019. Back then the CLI was still called prisma2. Unfortunately that did not include format as command yet, and I could not figure out easily which VSCode extension version was current back then. Going by the date, it could have been around ~0.0.20 which I could install in my VSCode. Buuuuut - it does not format my schema at all for some reason - so I can not reproduce.

But we indeed did relations totally different back then and only changed it during the beta period. So I would say that of course you are getting older (every day), what you are remembering might indeed be true. It might also be that back then we did not add any back relation fields at all really, that also got only added at a certain point, but I can not find that out right now.

So for now I would close this as “works as intended” and would ask you to possibly create an issue at https://github.com/prisma/prisma/ if you care about this behavior of the formatter (because the VSCode extension only uses that for this functionality, so the issue is better over there).