Document usage of customHttpAgent parameter
Closed this issue · 1 comments
It looks like support for adding a customHttpAgent when initializing the client was added in this PR in response to this request. The configuration documented in the README does not show this field or explain what it is or what it's used for, it would be helpful to update that especially since ava-typescript won't let you initialize the client without passing that information.
Additionally, can that field be made optional for those who don't need to pass a custom agent?
@sn1020 We updated the readme example to include some information on passing in a custom HTTP agent. Furthermore, ava-typescript will now be deprecated and unpublished as we released Typescript with the 22.11.1 release on 11-03-22 for Avatax, please point to that release as it will be what we use for Typescript and Javascript moving forward.
One of the changes that was made with that release is the customHttpAgent is an optional parameter for the constructor of ApiClient, so the issue you were having above should be resolved.
Please feel free to share any additional feedback!