Skip to content
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

Content Encoding does not support multiple comma separated content types #378

Closed
mattpolzin opened this issue Jul 18, 2024 · 0 comments · Fixed by #379
Closed

Content Encoding does not support multiple comma separated content types #378

mattpolzin opened this issue Jul 18, 2024 · 0 comments · Fixed by #379
Labels
bug Something isn't working v3.x

Comments

@mattpolzin
Copy link
Owner

For the OpenAPIKit module only (OpenAPI 3.1 specification), we need to support multiple content types on an Encoding Object.

I think the way to do this without a breaking change will be to introduce a new contentTypes array here: https://github.com/mattpolzin/OpenAPIKit/blob/main/Sources/OpenAPIKit/Content/ContentEncoding.swift#L17.

We can deprecate the singular contentType property but still populate it when possible for backwards compatibility with earlier v3 releases of OpenAPIKit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v3.x
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant