Internal GraphQL schema marks JsonFilter types as DateTime

Discussed in https://github.com/prisma/prisma/discussions/9116

<div type='discussions-op-text'>

^{Originally posted by RobertCraigie September 3, 2021} While looking into adding support for Json types to https://github.com/RobertCraigie/prisma-client-py I looked through the generated GraphQL schema and noticed that the JsonFilter type takes values of DateTime type, I would’ve expected to see either Json or String. Should be noted that this happens with and without the preview feature enabled.

Just curious as to whether or not this is intentional.

input JsonFilter {
  equals: DateTime
  not: DateTime
}

input JsonWithAggregatesFilter {
  equals: DateTime
  not: DateTime
  _count: NestedIntFilter
  count: NestedIntFilter
  _min: NestedJsonFilter
  min: NestedJsonFilter
  _max: NestedJsonFilter
  max: NestedJsonFilter
}
```</div>

[janpio]

https://github.com/prisma/prisma-engines/pull/2152 got merged that should fix it 👍

[janpio]

Ah ok, one level deeper then. We usually treat this as an internal implementation detail - if there is something weird, we will of course still look at it.