fix(TypeScript): Fix AxiosHeaders
types
#6696
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the TypeScript definitions for
AxiosHeaders
:Content-Encoding
header as an accessor. The{get,set,has}ContentEncoding
methods declared in the types and documented in the README did not actually exist at runtime and would throw an error. Now the runtime behavior matches the types.{get,set,has}AcceptEncoding
methods created by theAccept-Encoding
accessorget
accessors. For example,headers.getContentType()
returns the value of the content-type header. The return type was incorrectly declared asRegExpExecArray | null
when not passing aRegExp
.