oauth dependency (likely) incorrectly building the base string when qs contains nested objects

[jesuscript]

opened an issue in the respective library: request/oauth-sign#11

just wanted to bring someone's attention to the issue

[dbellavista]

Same issue. I'm stuck to request 2.47.1 because oauth is not working.

[nylen]

I didn't see the original issue, so thanks @dbellavista for commenting!

2.47.1 would be an unpublished version from GitHub, all our published versions end in .0. Is there a particular commit that you're using, or a commit that you've been able to identify as the breaking change?

[dbellavista]

Sorry, my mistake. I'm using 2.47.0. I noticed the error when a npm update upgraded request to 2.51.0.

[nylen]

OK, it's most likely a result of #1228 then, which landed in 2.48.0. @dbellavista @jesuscript any chance that one of you can provide a failing test case?

[dbellavista]

Uh.. While I was working at the minimal working example, I discovered that my problem is not related with this issue, but with the presence of charset=UTF-8 in the content-type header.
I have opened #1313