Mario DeSousa

Looks like there is a special enum value to do it: `Prisma.DbNull` From [Working with json fields](https://www.prisma.io/docs/concepts/components/prisma-client/working-with-fields/working-with-json-fields) ``` import { Prisma } from '@prisma/client' prisma.log.create({ data: { meta: Prisma.DbNull, },...

Yes, that works @MichalLytek ... but it's pretty weird behavior... setting to `null` seems more natural and consistent with how it works for other data types

That makes sense to me @MichalLytek. FYI, Prisma prevents null assignment through type checks (see below).  I think the issue in typegraphql-prisma is that assigning null is allowed by...

Yes @Jason3S , you are right... validators do have the same information. However, validators actually did their part by supporting if-then-else and would say "Instead of using an anyOf json-schema,...

Definitely wouldn't propose to alter the generation in ways that could break existing implementations. Using an opt-in annotation like the one proposed would mean that everything is generated the same...

Getting a fix for this would be great! I'm new to ts-json-schema-generator, and was banging my head because my definitions were coming back empty since we always export at the...

Hi, I was wondering about the status of this PR? Support for bound parameters is an important security feature... thanks!

as a workaround while the issue is fixed, we've added `@aws-sdk/middleware-endpoint` to our package.json and that solved the problem

hi @kettanaito , thanks for the help (and for the great library 👍 ) we are using basic authentication as [documented here](https://axios-http.com/docs/req_config) ``` auth: { username: '[email protected]', password: 's00pers3cret' }...

the username is an email address, e.g. `[email protected]`. the axios docs are generic, but it's common for many web services to use an email as the username.