-
Notifications
You must be signed in to change notification settings - Fork 46
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
Adapt to change in superagent lib #68
Adapt to change in superagent lib #68
Conversation
The functionality of the function in question seems to be the same, just a name change as far as I can tell. |
Actually, the checks failing seem to indicate this does not work |
Thanks. It may be just because Travis installs superagent 3.5 and your fix is not backward compatible. Try with the latest version in |
I don't think it's just Travis ... I think it's not a drop-in replacement. I am playing around with it to see if I can get it to work. But yes, it does seem like a major version type thing. Possibly it could gracefully revert if there's a way to detect which superagent API version is being used. |
Logic in the "old" This code seems to be gone, period, after their refactor. Not sure what might be, or not, handling that now. |
@DevSide So, I have the tests working now, but not sure if this is the right solution. As mentioned above, when |
@DevSide I just added a little bit for backwards compatibility. This passed the tests on both |
You are right, they actually stringify query in So what about: if (this._finalizeQueryString) {
isNodeServer ? this.request() : this._finalizeQueryString():
} else {
// superagent < 3.6
[...old code]
} ? |
Yeah that seems right. If I get a chance today I will play around with it and update the branch / PR |
@DevSide see latest. Uses |
Good ! Last request, could you upgrade superagent to ^3.6.0 in peerDependencies and devDependencies please ? |
Done! |
Is this PR ready to go? Would love a new version to stop the 'Unsupported' messages and traces spamming my console 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Thanks for your contribution ! 💪 |
Published on npm v3.6.0 |
Excellent - thanks for getting it progressed everyone. |
No problem -- we find |
To address issue #67