swagger-api / swagger-api/swagger-codegen
[typescript-fetch] Response headers are not available
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Response headers are not available on generated APIs for the typescript-fetch generator. A similar issue was recently fixed for the typescript-angular generator (#6902).
Swagger-codegen version
2.4.0-SNAPSHOT
Swagger declaration file content or url
https://github.com/swagger-api/swagger-codegen/blob/master/modules/swagger-
codegen/src/test/resources/2_0/petstore.yaml
Command line used for generation
swagger-codegen generate -i modules/swagger-codegen/src/test/resources/2_0/petstore.yaml -l typescript-node -o samples/client/petstore/typescript-node/default"
Steps to reproduce
Related issues/PRs
#6902 for typescript-angular generator
Suggest a fix/enhancement
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 running the shown generation command with modules/swagger-codegen/src/test/resources/2_0/petstore.yaml and inspect the generated typescript-fetch API responses. Compare the behavior with the typescript-angular fix in issue #6902; done means generated APIs expose response headers and the behavior is covered by an appropriate regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100