Closed jacobsmith closed 2 years ago
Thanks @jacobsmith - would you be able to add a test case to cover this please?
Sure thing @bernardd
@bernardd just added a very simple test. Let me know if there's a better place to add the test. Thanks!
@bernardd is there anything else we can do to help move this along?
Hey - sorry, been super busy with work. I'm hoping to catch up on this and other items this weekend.
@bernardd No worries - thanks for all your work on this/these libraries! We're currently running a fork with this one patch applied, so definitely not a blocker for us, but for obvious reasons we don't want to maintain a fork forever (:
Thanks again @anthonator and apologies for the delay getting this in.
@jacobsmith is the guy to thank but thanks for getting this merged in @bernardd!!!
Thanks @bernardd !
Whoops - thanks @jacobsmith :)
Passing Headers, such as
If-Match
, was previously causing issues. This is because the following code was executing when passing an array of header values:which destructured the data from
[{ "header-name", "header-value"}]
to{ "header-name", "header-value"}
(note that it is no longer a list containing a tuple, but rather simply a tuple.This caused issues later when trying to build up the headers to send in the request. Abbreviated for simplicity, we had:
Because
headers
was no longer aList
, theheaders
variable now contains an improper List.This change passes
config.headers
through to the underlying functions without destructuring it first.