Manuel Spigolon

I think the culprit has been already found: - fastify v4 uses ajv-format v2: https://github.com/fastify/ajv-compiler/blob/v3.6.0/package.json#L51 - fastify v5 uses ajv-format v3: https://github.com/fastify/ajv-compiler/blob/v4.0.2/package.json#L81 > There is a workaround to add backwards...

You need to check the tags&dependancies. Eg: https://github.com/fastify/fastify-request-context/tree/v3.0.0?tab=readme-ov-file In this case it is the `v3`, but it is just a case that it is compatible with fastify v3. TBH I...

I think this plugin can be used to do that: https://github.com/fastify/fastify-response-validation

Let's take into account a real use case as: https://github.com/fastify/fastify/pull/5917 I think the describe avoid the `setup()` initialization and traces the border of complex tests or in some way speed...

> Should I be adding 'query' to that array? No, that code does not affect `light-my-request/lib/config-validator.js`, it generates the `req.query()` method shortcut (that we are missing and still it is...

Is the plugin registered before the route definition?

Not a strong TS user here, but I tend to agree that the only status codes accepted should be the ones listed by the user. I can see only an...

The validator should return an `{ error }` instead of throwing it: ``` function (data) { try { const result = schema.validateSync(data, yupOptions) return { value: result } } catch...

Thanks for willing to help! I can see 3 PRs: 1. Documentation: it is not well explained that we should return the error. it is mentions here and there: https://fastify.dev/docs/latest/Reference/Validation-and-Serialization...

Reopening: https://github.com/fastify/fastify/issues/6214#issuecomment-2988080107 I will work on 2 in few weeks if somebody does not pick it up before