We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description
When there is no response content, header types are not exported. I believe this is caused by these lines: https://github.com/drwpow/openapi-typescript/blob/efbc4498ef04ff303ab0804451a701acd7fc5196/packages/openapi-typescript/src/transform/response-object.ts#L13-L14
This affects HEAD requests
openapi-typescript
6.3.9
20.4.0
MacOS Ventura
Reproduction
If run openapi-typescript on this example spec: https://gist.github.com/jacobshirley/96f18b0244d927146ef66a09c6110594 - it will not output types for X-Document-Reference. It will output 'never' for the 200 response.
Expected result
It should output the X-Document-Reference type
Checklist
npx @redocly/cli@latest lint
The text was updated successfully, but these errors were encountered:
This is a bug, but is a duplicate of #1109, so I’ll close this in favor of that one.
Sorry, something went wrong.
No branches or pull requests
Description
When there is no response content, header types are not exported. I believe this is caused by these lines: https://github.com/drwpow/openapi-typescript/blob/efbc4498ef04ff303ab0804451a701acd7fc5196/packages/openapi-typescript/src/transform/response-object.ts#L13-L14
This affects HEAD requests
openapi-typescript
6.3.9
20.4.0
MacOS Ventura
Reproduction
If run openapi-typescript on this example spec: https://gist.github.com/jacobshirley/96f18b0244d927146ef66a09c6110594 - it will not output types for X-Document-Reference. It will output 'never' for the 200 response.
Expected result
It should output the X-Document-Reference type
Checklist
npx @redocly/cli@latest lint
)The text was updated successfully, but these errors were encountered: