-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple ContentTypes per route #648
Comments
Different feature, but maybe also interesting to support: fastify/fastify#5545 |
Looks like you are right. Supporting it seems to be relatively easy by modifying the v2/v3 parsers a little. I will look into it. Kind regards, |
And while we are at it, the same holds for this one. Thanks for reporting. Kind regards, |
ps. the fix is easy as both requestBody and responses are parsed by: fastify-openapi-glue/lib/Parser.v3.js Lines 99 to 112 in 0d73494
Most work, as often, however will be creating the proper tests. I'm a few days away from my dev setup so it might take a while before its done. Kind regards, |
Feature added by #650 , published as 4.9.0 on NPM. Kind regards, |
The README.md says 'fastify only supports one schema per route.'
I don't think that it true anymore, see fastify/fastify#4264 and https://fastify.dev/docs/latest/Reference/Validation-and-Serialization/#serialization
Am I correctly interpreting the Fastify documentation? If so, could this plugin be amended to properly support response schema's per content per result code?
The text was updated successfully, but these errors were encountered: