You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In details, I return some 200 HTTP responses with different schemas, however the current swagger of Flask-restx has not supporting the 'oneOf' in response schema. This disallows me to resolve my problem.
I want to refer this comment on the above issue in order to clear my desire.
The text was updated successfully, but these errors were encountered:
Reading the linked OpenAPI Spec ticket, they're citing this as addressed with anyOf and oneOf and the various things added in OpenAPI 3.0
From that would you (and other readers) accept that a move to include OpenAPI 3.0 as a way to meet this request? Or do you want something more like what was originally asked for and debated?
The issue will be that flask-restx may be able to create different schemas, but we'll fall into some major issues because it won't be supported the same way in OpenAPI 3.0. That means things like "we'll have to make 2 specs, with different links" or something like that (which is probably not super desirable).
Gut check says "different responses with different schemas = different endpoint" which is a distillation of part of the discussion in the spec.
I want to request a feature in Flask-restx which is similar to one describing in OAI/OpenAPI-Specification#270
In details, I return some 200 HTTP responses with different schemas, however the current swagger of Flask-restx has not supporting the 'oneOf' in response schema. This disallows me to resolve my problem.
I want to refer this comment on the above issue in order to clear my desire.
The text was updated successfully, but these errors were encountered: