fastify-type-provider-zod issues

Update zod-to-json-schema to latest version, expose zod-to-json-schema options on createJsonSchemaTransform

1

This will be very useful, for example modifying the contentEncoding for binary files when using a `z.string().base64()` with latest zod(3.23)

thelinuxlich

feat: added refs and separated the type providers

1

I added a way to add refs to your schema and modified the type provider correctly for when this PR is accepted: https://github.com/fastify/fastify/discussions/5311

Bram-dc

204 response without content

2

Currently, fastify-swagger allows the specification of a 204 without any content: https://github.com/fastify/fastify-swagger?tab=readme-ov-file#empty-body-responses ``` { response: { 204: { type: 'null', description: 'No Content' }, 503: { type: 'null', description: 'Service...

EricSmekens

How to specify examples?

2

For use with fastify-swagger, I'd like to be able to add examples at the property level and at the schema level. From reading the code, it seems like this library...

JaneJeon

NPM Module not up to date with github repo

4

The NPM Module is outdated and lacks features as `FastifyPluginAsyncZod`.

BenjaminLindberg

Schemas and hooks

5

I have custom JwtAuth hook and I use it on specific routes. ``` export const jwtAuth: preValidationHookHandler = (request, res, next) => { if (request.headers.cookie) { try { const token...

sbeben

validation fail for params of type numbers. expects a string

2

example: the following route if you open `http://127.0.0.1:3003/x/12` it will fail `expected number, received string`. ``` fastify.withTypeProvider().get("/x/:n", { schema: { params: z.object({ n: z.number() }), response: { 200: z.object({ n:...

alzalabany