Validator accepts arbitrary properties in datasource blocks

[janpio]

Bug description

This schema is happily accepted:

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

datasource db {
  provider          = "mysql"
  url               = env("DATABASE_URL")
  shadowUrlDatabase = env("SHADOW_DATABASE_URL")
  foo               = bar
}

That is unfortunate, as shadowUrlDatabase should really be shadowDatabaseUrl instead, and foo of course does nothing as it is not a known property.

Prisma Version

2.23.0

[do4gr]

For datasources we only allow a specific set of properties. And for the only the prisma-client-js generator as well. Other generators can have arbitrary properties.

[pimeys]

We do have an arbitrary key/value storage in the generator. I don't want to touch those validations, but datasource we know and can validate what should not be there.

[janpio]

We do have an arbitrary key/value storage in the generator

If provider = "prisma-client-js" then we also have a defined list of properties that are possible. If we can scope this validation to this generator.provider value, we can give our users value.

[janpio]

Follow up in #11825