[BUG] [Typescript] Response headers are not available.

[acabarbaye]

Bug Report Checklist

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator (example)?
• Have you tested with the latest master to confirm the issue still exists?
• Have you searched for related issues/PRs?
• What's the actual output vs expected output?
• [Optional] Sponsorship to speed up the bug fix or feature request (example)

Description

I want to access the response headers for an E-tag. In the openAPI yaml file, the headers are defined for the response but it doesn't generate anything to access them

      responses:
        '200':
          description: Resource returned OK.
          headers:
            Cache-Control:
              $ref: '#/components/headers/CacheControlHeader'
            ETag:
              $ref: '#/components/headers/ETagHeader'
            Version:
              $ref: '#/components/headers/VersionHeader'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/....'

the header is defined as follows:

    ETagHeader:
      description: 'Caching: An opaque string which identifies a specific version of the returned resource.'
      schema:
        type: string

The problem with the headers in the response not being accessible (especially E-tag) seems to be faced by other typescript-xxx client generators #6527

[davidediak]

any news on this? I'd also want to retrieve the ETag header

[excavador]

Any updates?

[Robbilie]

@excavador Check this out, it's already available:

#16260

[purrden]

Hi @Robbilie, can you please advise if I need to provide any specific settings via config to the generator to get methods with WithHttpInfo suffix?

[Robbilie]

They should be included by default since the new methods are used by the old ones. I'm still using my own branch for generating the client and haven't tried with the main branch

[excavador]

@Robbilie Shell we close this issue as resolved?

[Robbilie]

I think my PR solved this, even though t doesn't necessarily enforce the types that are defined in the openapi spec it at least grants access to them