Request to support coerceTypes for each part of an HTTP message separately. about fastify-openapi-glue

[seriousme]

Thanks for asking.

ajvOptions are passed verbatim to the AJV validator and AJV only supports coerceTypes and not:

coerceParms: true | false,
coerceBody: true | false,
coerceQueryString: true | false,
coerceHeaders: true | false

Which makes sense if you know that Fastify uses a single AJV instance for all of the 4 parameter locations on a given route.
AJV does not even know where the data comes from , it is Fastify that knows about these locations ;-)

I'm a bit curious as to why you want to apply different coercion rules to different parts of the message ?
Do you have an actual problem that needs to be solved ?
It might be possible to disable coercion, however that might require a more complex schema.

If you really feel that these options are important to you then I'd suggest to post an issue at Fastify to get it solved there. Once Fastify supports it you can configure Fastify before registering fastify-openapi-glue.

Hope this helps.

Kind regards,
Hans

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days'