Why is accept hard coded? Can it be changed to */* until a better solution is created?

[PaulDotmatics]

Description

const headers = Object.entries({
	Accept: 'application/json',
	...additionalHeaders,
	...options.headers,
})

Why is it hard coded to application/json wouldnt */* be better?

OpenAPI specification (optional)

No response

Configuration

N/A All of them do it

System information (optional)

No response

[mrlubos]

What's the use case @PaulDotmatics?

[PaulDotmatics]

My current use case is im calling an api that requires accept: application/octet-stream and if I send JSON it says unsupported because im telling it my client only supports application/json.

Seems that openapi-ts can support application/octet-stream in content type but not in accept.

[mrlubos]

Have you looked at the new Fetch API client? You should be able to send any request with it

[PaulDotmatics]

I have and it doesnt help me because it would change all my code too much

[mrlubos]

Can you elaborate on what kind of changes would be required? You could always generate a separate client and migrate gradually instead of doing everything in one go

[benjamalin]

Issue is that generator doesn't take into account open api response content type.

if you have
get :
...
responses:
default:
description: OK
content:
text/plain:
type: string

your server will not accept query from generated client.

Of course you can still do it before request through Fetch api client but 1. you have to do it even if it is already in openapi declaration and 2. you still have to migrate to fetch api client