Repository navigation
Ignore Content-Type parameters #658
Description
Activity
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?
path: /path: get: responses: '200': content: application/json; version=2.3.5: schema: $ref: '#/components/schemas/Model23' application/json; version=2.4.0: schema: $ref: '#/components/schemas/Model24'
I guess the parameters should only be ignored only when selecting a decoder, and even then, maybe use the encoding param
- locked and limited conversation to collaborators
on Aug 13, 2023
Is your feature request related to a problem? Please describe.
RFC2616 allows parameters to content-types, for example
application/json; version=2.3.5is 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