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
{{ message }}
Repository navigation
V3 multipart encoding property type for content-type isn't supported #308
I would not expect any errors or lack of the contentType for message when reading the YAML. I do get a diagnostic error: "encoding is not a valid property at #/paths//convert/post/requestBody/content"
Diving into the code a bit, Microsoft.OpenApi.Readers\V3\OpenApiMediaTypeDeserializer.cs / _mediaTypeFixedFields has a comment like a todo for encodings, but its left unimplemented.
Activity
daniel-white commentedon Aug 7, 2018
Diving into the code a bit,
Microsoft.OpenApi.Readers\V3\OpenApiMediaTypeDeserializer.cs/_mediaTypeFixedFieldshas a comment like a todo for encodings, but its left unimplemented.daniel-white commentedon Aug 7, 2018
Well it looks like the rest of the plumbing is there; this is what is missing in the
_mediaTypeFixedFieldsPerthCharern commentedon Oct 1, 2018
Based on the PR and the conversation above, I believe this is resolved. Please reopen if that's not the case.