You might want to wait until #4140 is merged, because it adds a new HeadersDefaults interface with essentially 11 occurences of Record<string, string> that could be replaced by the new AxiosHeaders type.

@caugner #4144 does exactly that

@caugner #4144 does exactly that

👍 for differentiating RequestHeaders and ResponseHeaders, but this PR extends the type to string | string[], whereas #4144 extends the type to string | number | boolean | undefined.

The common ground would be to keep RequestHeaders as Record<string, string> and have ResponseHeaders distinguish between set-cookie (string[]) and other headers (string).

@caugner #4144 does exactly that

👍 for differentiating RequestHeaders and ResponseHeaders, but this PR extends the type to string | string[], whereas #4144 extends the type to string | number | boolean | undefined.

The common ground would be to keep RequestHeaders as Record<string, string> and have ResponseHeaders distinguish between set-cookie (string[]) and other headers (string).

Haha sorry – I was referring to that PR assigning things to type aliases, I should have clarified that! Was sharing that the two PRs could build from one another 😄

Actually, #4117 was the first PR to suggest adding a Headers type.

It would probably make sense to introduce a specifc AxiosHeaders type:

type AxiosHeaders = Record<Exclude<"set-cookie", string>, string> & {
  "set-cookie"?: string[]
}

I like this idea! But it doesn’t work. After some fiddling I came up with:

type AxiosHeaders = Record<string, string> & {
  "set-cookie"?: string[]
}

playground link

Also we may want to differentiate between request and response headers, as set-cookie is only defined as string[] in the response headers.

type AxiosRequestHeaders = Record<string, string>;

type AxiosResponseHeaders = Record<string, string> & {
  "set-cookie"?: string[]
};

It would probably make sense to introduce a specifc AxiosHeaders type:

type AxiosHeaders = Record<Exclude<"set-cookie", string>, string> & {
  "set-cookie"?: string[]
}

I like this idea! But it doesn’t work. After some fiddling I came up with:

type AxiosHeaders = Record<string, string> & {
  "set-cookie"?: string[]
}

playground link

Also we may want to differentiate between request and response headers, as set-cookie is only defined as string[] in the response headers.

type AxiosRequestHeaders = Record<string, string>;

type AxiosResponseHeaders = Record<string, string> & {
  "set-cookie"?: string[]
};

I have a question about this code, type AxiosResponseHeaders = Record<string, string> & { "set-cookie"?: string[] };, i wrote some codes here playground, but there are some error and i can't understand it, so could anyone help explain the reason?

i wrote some codes here playground, but there are some error and i can't understand it, so could anyone help explain the reason?

@EyebrowsWhite Not sure why it doesn't work when declaring the header object directly, but the following works (see playground):

type AxiosHeaders = Record<string, string> & {
  "set-cookie"?: string[]
}

declare let headers: AxiosHeaders;

headers = {}
headers['Content-Type'] = 'text/plain'
headers['set-cookie'] = ['abc', 'def']