swagger-api / swagger-api/swagger-codegen
Not getting headers in response for android client
Open
Nobody has claimed this yet.
Client: Android
Enhancement: Feature
General: Question
help wanted
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
I have generated code for android client that uses volley library. I want to get headers from response. How can i get the headers from the response ???
Swagger-codegen version
swagger-codegen-cli-2.2.1.jar
Swagger declaration file content or url
paths:
/login:
post:
summary: send mobileNum and otp to login
description: send mobileNum and otp to login
parameters:
- name: args
in: query
description: send mobileNum and otp in args
required: true
type: string
format: string
tags:
- login
responses:
'200':
headers:
Authorization:
description: access token will be set in the authorization header
type: string
description: login successful, received accessToken in header and refreshToken in body
schema:
$ref: '#/definitions/ResponseTO'
```
##### Command line used for generation
java -jar swagger-codegen-cli.jar generate -i login1.yml -l android --library=volley -o login-source-code/ -c config.json
=> for adding header to the request, i can use the following code,
LoginApi loginApi = new LoginApi();
loginApi.addHeader(String key, String value)
=> How can i get the headers from the response ??????
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 with the generated Android client using the Volley library and trace the response handling for the /login operation. Verify how the declared Authorization response header is exposed, and consider the work complete when callers can access response headers from the generated login request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100