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
Is your feature request related to a problem? Please describe.
RFC2616 allows parameters to content-types, for example application/json; version=2.3.5 is a valid content type that should be treated like application/json. Currently this is not supported by this project.
Describe the solution you'd like
Ignore any parameters (things including and after ;) in the content type.
On another thought, can the parameters be used as a discriminator? I mean is it valid OpenAPI with multiple responses for the same path, method and content type differing only with a parameter?
Is your feature request related to a problem? Please describe.
RFC2616 allows parameters to content-types, for example
application/json; version=2.3.5
is a valid content type that should be treated likeapplication/json
. Currently this is not supported by this project.Describe the solution you'd like
Ignore any parameters (things including and after
;
) in the content type.Describe alternatives you've considered
Using #657.
Additional context
#655
The text was updated successfully, but these errors were encountered: