Message: Request textDocument/definition failed with message: Schema parsing

[janpio]

[Info  - 15:50:38] Installed version of Prisma binary `prisma-fmt`: 0c2ec197653b278b2978845ef958db88824cd82e
[Error - 17:48:15] Request textDocument/definition failed.
  Message: Request textDocument/definition failed with message: Schema parsing
�[1;91merror�[0m: �[1mError validating source `postgresql`: The URL for datasource `postgresql` must start with the protocol `postgresql://`.�[0m
  �[1;94m-->�[0m  �[4mschema.prisma:3�[0m
�[1;94m   | �[0m
�[1;94m 2 | �[0m  provider = "postgresql"
�[1;94m 3 | �[0m  url      = �[1;91m"foo"�[0m
�[1;94m   | �[0m

Validation Error Count: 1
  Code: -32603 

Model:

datasource postgresql {
  provider = "postgresql"
  url      = "foo"
}

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

model User {
  id      Int     @default(autoincrement()) @id
  email   String  @unique
  name    String?
  role    String?
  storeId Int?
}

model Product {
  id          Int     @default(autoincrement()) @id
  handle      String  @unique
  name        String?
  description String?
  price       Int?
}

Happened when I replaced the invalid foo with postgresql://foo and a real connection string.

[carmenberndt]

I can not reproduce this. Does this also happen when you use this connection string: url = "postgresql://johndoe:mypassword@localhost:5432/mydb?schema=public"?

[janpio]

No.

I can reproduce this when I paste the schema above, then select foo in the editor and paste postgresql://foo over it after trying a few times.

[carmenberndt]

I can reproduce this, but not exactly how you are describing this. When using your model with foo and then clicking Go to Definition on any value, this error occurs. This is expected though, since formatting is only possible on valid input files.

[janpio]

I could now even reproduce it when I had this schema:

datasource postgresql {
  provider = "postgresql"
  url      = "foo"
}

// postgresql://foo

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

model User {
  id      Int     @default(autoincrement()) @id
  email   String  @unique
  name    String?
  role    String?
  storeId Int?
}

model Product {
  id          Int     @default(autoincrement()) @id
  handle      String  @unique
  name        String?
  description String?
  price       Int?
}

When selecting and dragging on postgresql://foo to copy/paste it, the error triggered.

This is expected though, since formatting is only possible on valid input files.

Shouldn't this always be just a red squiggly underline instead of a toast and a nasty message in the output?

[carmenberndt]

This will be fixed by #129 because textDocument/Definition does not parse the schema anymore using the sdk.

[janpio]

I could indeed not reproduce this with dev 0.0.1250 any more 🚀