You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In practice, I've found that the best place to pay attention to headers is within the tests themselves.
When a request is made, I think it's better to have something like x-recorder-headers: ["x-test-id", "x-custom-header"] to specify what you want to keep.
There seems to be more surprises by how hashing operates, considering
headers
.So, either there could be a
hash
option for customizing...Or,
normalize
can choose to return the normalized object (instead of mutating), where returningundefined
will keep normal normalization.(I still think that Polly.js does a good job of hashing headers with
matchRequsestsBy
: https://netflix.github.io/pollyjs/#/configuration?id=defaults)The text was updated successfully, but these errors were encountered: