jsonProtocol: in argument of filter types does not accept scalars

[SevInf]

Bug description

When GraphQL protocol is used, we accept scalar fields for in arguments because this shortcut is implemented on the client. With jsonProtocol, client-side shortcut no longer exists and engine rejects this code.

How to reproduce

1. Run the provided code. Get the validation error:

   Argument `in`: Invalid value provided. Expected String[], provided String.
   

2. Remove jsonProtocol preview feature from the schema, re-generate code and re-run the schema. It will finish without an error.

Expected behavior

Identical behavior regardless of the protocol

Prisma information

generator client {
  provider        = "prisma-client-js"
  output          = "../node_modules/.prisma/client"
  previewFeatures = ["jsonProtocol"]
}

datasource db {
  provider = "sqlite"
  url      = "file:./dev.db"
}

model User {
  id String @id
}

await prisma.user.findFirst({
    where: {
      id: { in: '123' },
    },
  })

Protocol request:

{
  "modelName": "User",
  "action": "findFirst",
  "query": {
    "arguments": {
      "where": {
        "id": {
          "in": "123"
        }
      }
    },
    "selection": {
      "$composites": true,
      "$scalars": true
    }
  }
}

Environment & setup

• OS: any
• Database: any
• Node.js version: any

Prisma Version

4.11.0+

[janpio]

Current workaround until this is fixed:
Replace id: { in: '123' }, with either id: "123" or id: { in: ["123"] }.