Misleading env error on client binaryTargets

Problem

I normally build different Prisma clients for different environments e.g. darwin or rhel-openssl-1.0.x. As a result, I use an environment variable on the client.binaryTargets field in the schema file. However, it always shows squiggly red lines saying the environment variable does not exist:

Note how the db.url field is also using environment variable but is not seen as errors.

Suggested solution

Can we treat the client.binaryTargets the same as the db.url field please 😃 ?

Alternatives

Alternatively, I think we can start vscode with the environment variable but it’s not recommended

Additional context

This is not actually causing errors when running commands in CLI if env variables are supplied correctly. This just shows the schema file as if there’s always an error which potentially hides other errors

[Jolg42]

Was probably fixed since it was reported.

[Jolg42]

Could not reproduce the squiggly red lines with most recent version with

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  binaryTargets   = [env("SOMETHING")]
}