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.
This is a very similar issue as #440 but for Javascript. Here is an example endpoint with multiple representations that could be returned (csv or json):
* Chooses a content type from the given array, with JSON preferred; i.e. return JSON if included, otherwise return the first.
* @param {Array.<String>} contentTypes
* @returns {String} The chosen content type, preferring JSON.
*/{{/emitJSDoc}}
jsonPreferredMime(contentTypes) {
for (var i = 0; i < contentTypes.length; i++) {
if (this.isJsonMime(contentTypes[i])) {
return contentTypes[i];
}
}
return contentTypes[0];
}
Describe the solution you'd like
I would like to be able to describe multiple produces parameters with different content types as documented in OpenAPI 3 and all of those be passed to the server. It would be nice to have full deserialization support for all of the different content types like in the Python PR, but at a minimum all content types should be sent in the Accept header.
Describe alternatives you've considered
A workaround for me is to remove the secondary JSON response altogether, leaving only the CSV response. Since I was coming from Swagger 2 codegen anyway that only allowed a single media type, this solution worked for me as a stop-gap.
Additional context
None!
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
This is a very similar issue as #440 but for Javascript. Here is an example endpoint with multiple representations that could be returned (csv or json):
This generates the following API:
This all looks correct. But, the generated
apiClient.callApi
only ever returns a single mime type, and alwaysapplication/json
if it is included:openapi-generator/modules/openapi-generator/src/main/resources/Javascript/es6/ApiClient.mustache
Lines 185 to 198 in 99d8371
Describe the solution you'd like
I would like to be able to describe multiple
produces
parameters with different content types as documented in OpenAPI 3 and all of those be passed to the server. It would be nice to have full deserialization support for all of the different content types like in the Python PR, but at a minimum all content types should be sent in theAccept
header.Describe alternatives you've considered
A workaround for me is to remove the secondary JSON response altogether, leaving only the CSV response. Since I was coming from Swagger 2 codegen anyway that only allowed a single media type, this solution worked for me as a stop-gap.
Additional context
None!
The text was updated successfully, but these errors were encountered: