Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

status "unknown" on response error

Open Beginner friendly
  • Is something wrong?
#342 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
tooling

Research direction

Start in plugins/typescript/src/templates/fetcher.ts at the response-error handling around line 107, using the linked revision as the reference point. Trace how the generated fetcher assigns the status for non-ok responses and confirm the expected value against the issue description. Done means the behavior is clarified or corrected so the generated error status reflects the response status when appropriate.

Written by the indexing model from the issue text.

Description

What's the reason to set status: "unknown" when the response is not ok? From my understanding it should be totally fine to simply use response.status in that case:

https://github.com/fabien0102/openapi-codegen/blob/aac52caee5210cd4cbbc54ca0314d0e38ee79618/plugins/typescript/src/templates/fetcher.ts#L107

Dominant language
TypeScript
Stars
634
Forks
83
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fabien0102/openapi-codegen

All issues in fabien0102/openapi-codegen

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.