OpenAPITools / OpenAPITools/openapi-generator
[BUG] Support for consumes in @RequestMapping not working
Open
Nobody has claimed this yet.
Issue: Bug
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Instead of
@RequestMapping(value = "/tracks", method = RequestMethod.POST, consumes = {MediaType.MULTIPART_FORM_DATA_VALUE})
One has to go with @ApiResponse in order to get Content-Type set in the generated code.
@RequestMapping(value = "/tracks", method = RequestMethod.POST)
@ApiResponse(description = "Successful Operation", responseCode = "200", content = @Content(mediaType = MediaType.MULTIPART_FORM_DATA_VALUE))
The first generated
const httpHeaderAccepts = [
'*/*'
];
instead of
const httpHeaderAccepts = [
'multipart/form-data'
];
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Reproduce the shown Java @RequestMapping case and inspect how the generator produces the TypeScript request headers; compare it with the @ApiResponse workaround. Done means consumes=MediaType.MULTIPART_FORM_DATA_VALUE results in a generated Content-Type or media-type value of multipart/form-data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi, typescript
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100