-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Discriminator support in JSON samples #459
Comments
I also have this question. This would be a great feature that would allow people to maintain their examples just by documenting/updating their requests and responses. The current alternative/work-around is to explicitly define examples for each discriminator choice which is obviously cumbersome from a documentation maintenance perspective. That said, I'm sure this isn't a small request. It would be nice to know if it's on the road map and/or when it might be prioritized. Given the current state of the examples in my documentation, I would likely be able to contribute to this on-the-clock. :-) |
Digging into this a bit, it looks like it works if you define the request body as a UPDATE: Nope. That's not quite right either. I tried some things based on what the OP of this thread -- #524 -- was able to achieve, but I could not duplicate his results. |
I too experience problems when using |
@RomanGotsiy Any thoughts or updates on this? |
Anyone has any update or example of how to achieve this? |
Yes, this is a bit annoying. Any plans going on tackling this one? |
@RomanHotsiy Has there been any progress on this? |
Bump! |
Are there plans, following the upgrade to 2.0 to support discriminated fields in JSON payloads? Currently these are not included in the examples.
The text was updated successfully, but these errors were encountered: