-
-
Notifications
You must be signed in to change notification settings - Fork 322
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 oneOf
when describing requestBody
#193
Comments
Hi there, Any ETA for this feature? Thanks :) |
No ETA at the moment, I'm afraid. Pull requests would be very welcome! |
Thanks for your answer, I'll look if I can do something |
Hi, do we have any ETA on this ? If not can I get a summary of what needs to be changed with possible code pointers where to look for inspiration ? I guess this could be similar to the request response examples right ? Any pitfalls ? |
Generally unless an issue is tied to a milestone with a date on it, then there is no ETA. I'll try and take a look at what's (not) going on and either fix or write it up for someone else. |
is there still progress on this topic? having no proper support on oneOf/allOf renders the openapi-generator unusable for many use cases |
@manuelhartl do you mean |
Is your feature request related to a problem? Please describe.
I'd like a way to describe two request bodies to the same API path, but with somewhat different bodies. For example, say I have a
/user
path, and want to be able to create a regular user and amanager
user, where themanager
user has multiple other fields that need to be set.Describe the solution you'd like
The OpenAPI 3.0 spec supports
oneOf
forrequestBody -> content -> application/json -> schema
, per the docs:https://swagger.io/docs/specification/describing-request-body/
Right now if you use
oneOf
here, it doesn't show any of the requestBodies.Describe alternatives you've considered
I'm also tried using multiple requestBody examples per this other ticket I created, but unfortunately that isn't supported either.
The text was updated successfully, but these errors were encountered: