swagger-api / swagger-api/swagger-codegen-generators
Retrofit2 Accept Header not set
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 299
- Forks
- 439
- PR merge metrics
- No merged PRs in 30d
Description
If one generates a Retrofit2 client from the PET Store example, there is no Accept header set. This leads, at least for Spring based backends, to problems, since the accept header ist mandatory.
I don't know if i'm wrong, since retrofit2 is a popular framework and i think someone has to have the same issue?
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
Start by generating the Retrofit2 client from the PET Store example and inspect how request headers are produced. Compare the generated requests with the Spring backend requirement, then verify that the expected Accept header is present in the generated client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100