-
-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"this.mapHeaders is not a function" #99
"this.mapHeaders is not a function" #99
Comments
Not sure what scenario would cause this. Our tests don't reflect that, and I'm unable to reproduce using your example. Line 29 in the v2.0.0 tag source (which you're running) sets the options and asserts that mapHeaders cannot be undefined Line 26 in 97edb38
Line 37 in 97edb38
Line 69 in 97edb38
this is from the same scope as the previous line, on which this.headers exists.
Probably something you're going to have to investigate on your end and submit a patch or PR for. |
What? It's right here: Line 73 in 2c95c35
|
Sweet. Please open a PR and we'll merge your fix. |
I don't have a fix. I have no idea what that code does. How could yours work? I suppose that's the key to the bug. |
It looks like |
Happy to merge and publish a PR to fix. Just don't have the time to triage for another week or so. |
There must be something else (or more) at play.
I think @shellscape should first triage this so we fully understand the bug before attempting a fix. |
The root of the problem appears to be where the defaults are merged with the passed-in options. Line 29 in 2c95c35
map* functions as valid arguments. (Below code is from the v1.12.1 tag) Line 32 in d8791d3
The most obvious fix to me is to just revert back to the old option-parsing code, maybe just for the map functions. If that sounds ok to you, I can probably submit a PR some time this week. |
I agree with that analysis, but that doesn't explain why @shellscape is not able to reproduce it. I think that should be debugged first. |
(On a plane right now and the wifi is miraculously working) It might be a sticky global bin. My first step in every issue is to try and reproduce locally. If it's unreproducible for me, but reproducible for a bunch of others, then it's probably a wonk on my end. I wouldn't give my lack of reproduction much credence until I've got the time to investigate. I wouldn't recommend a reversion as a fix, but rather trying to get the new style to party correctly with the breaking changes in the major. |
Part of this may be to do with documentation error. The documentation on NPM shows
But the actual code is
|
Commit a22f006 resolves this. (Github looks to be having issues tonight) |
Expected Behavior
Actual Behavior
How Do We Reproduce?
The text was updated successfully, but these errors were encountered: