Is there is way to make Type.Date into Type.String when converting the DateTime from Prisma to TypeBox?

[brucelin006]

I am using Fastify, and I am trying to use the generated TypeBox type as the schema for the request and reply, however Fastify can only serialize the Type.Date if it is Type.String. Is there a way that Prismabox can have an option of choosing either Type.Date or Type.String?

Also, I am experiencing import issues for ESM, where the __nullable__ generated in the prismabox directory gives an error saying it has to be import { __nullable__ } from "./__nullable__.js";, but the original one does not come with .js, is there a way to append this by Prismabox?

[m1212e]

Also, I am experiencing import issues for ESM, where the nullable generated in the prismabox directory gives an error saying it has to be import { nullable } from "./nullable.js";, but the original one does not come with .js, is there a way to append this by Prismabox?

This seems like a misconfigured typescript/module resolution. When using ESM you should not be required to set the .js extension in your imports.

I am using Fastify, and I am trying to use the generated TypeBox type as the schema for the request and reply, however Fastify can only serialize the Type.Date if it is Type.String. Is there a way that Prismabox can have an option of choosing either Type.Date or Type.String?

This would cause type mismatches when using the schemas with prisma. You then could not pass them into or apply them to values coming/going in/out of prisma and are required to make manual mappers. This is because prisma enforces usage of JS Date objects.
I see this more as a fastify/serialization issue since prismabox tries to stick as close to the prisma specifications as possible. I'd recommend checking out serialization options or middlewares in fastify to tackle this issue.

[m1212e]

Sidenote: I can hightly recommend elysia over fastify, if you have a choice in tooling!

[m1212e]

Regarding the string thing you mentioned: Is this maybe related?

[m1212e]

This might be resolved by #11