Support multiple response body content types about swift-openapi-generator HOT 6 CLOSED

Added the design label, as this task will require a proposal, as it introduces a new paradigm - the Accept header hinting at the expected response Content-Type, where there isn't a single obvious solution, so should be discussed first.

from swift-openapi-generator.

It's also possible we could split this into two issues:

1. supporting multiple response body content types
2. providing the Accept header to the server to help it make a decision about which response content type to use

In this case, the first one would be straightforward, and not require a proposal - just like multiple request content types.

The second one would require a proposal.

from swift-openapi-generator.

providing the Accept header to the server to help it make a decision about which response content type to use

IMO this has to be part of the solution as it's the conventional way of telling the server what you want when it can provide different response types.

from swift-openapi-generator.

For sure, was just trying to break out the work that's non-controversial (supporting multiple content types) from the thing that needs design (how we provide the value for the Accept header to the adopter on the server). Not saying we would make a release with a partial implementation, just that these things can land in separate PRs, for easier review.

from swift-openapi-generator.

Landed in main under the multipleContentTypes feature flag.

from swift-openapi-generator.

Now released in 0.1.7 under the multipleContentTypes feature flag.

from swift-openapi-generator.