Prisma

Hello Prisma,

Any idea why the args of mongodb raw queries operations are under  `outputObjectTypes`  and not under `inputObjectTypes`  like all other operations?

<@U024DS62DRC> No, I meant all the raw operations for mongodb, like findRaw and aggregateRaw

In the dmmf, I see them in the output types

This op for example
``` {
              "name": "findAccountRaw",
              "args": [
                {
                  "name": "filter",
                  "isRequired": false,
                  "isNullable": false,
                  "inputTypes": [
                    {
                      "type": "Json",
                      "location": "scalar",
                      "isList": false
                    }
                  ]
                },
                {
                  "name": "options",
                  "isRequired": false,
                  "isNullable": false,
                  "inputTypes": [
                    {
                      "type": "Json",
                      "location": "scalar",
                      "isList": false
                    }
                  ]
                }
              ],
              "isNullable": false,
              "outputType": {
                "type": "Json",
                "location": "scalar",
                "isList": false
              }
            }```

Oh, I see you are talking about dmmf. I am not sure about the reasoning behind it. Is this causing an issue?

<@U024DS62DRC> Yes. In one of my generators, I loop over input types to generate Zod schemas. But these new operations args are not in the same place as others are.
For now I can filter output types for objects that have the `raw` string in it. But I think that isn't really a good solution.

Hmm, creating a <https://github.com/prisma/prisma/issues/new?assignees=&amp;labels=kind%2Fbug&amp;template=bug_report.yml|GitHub Issue> regarding this could be helpful. Prisma Client team might be able to provide insights on the reasoning behind this.

Done:
<https://github.com/prisma/prisma/issues/14900>