Ampersands breaking encoding about apps-script-oauth1 HOT 5 CLOSED

I tried to replicate the problem using my Twitter sample but ampersands were sent along just fine:

https://github.com/googlesamples/apps-script-oauth1/blob/master/samples/Twitter.gs

Are you doing anything different than that?

from apps-script-oauth1.

I am doing a few things differently as legacies to older workarounds, but it's good to see a working example. I'll try to bring mine more in line with your sample code and see if that clears it.

The main differences that stand out are that I'm using an enhanced encodeURIComponent function to also encode reserved characters like (,),!,*, etc., and then I'm setting escaping to false in the parameters object. Let me see if either those make a difference.

from apps-script-oauth1.

Ah yes, I see now. I was sending the payload as a string, like "status=some%20status%20with%20percent%20encoding", but I see now that the library expects the payload to be an object, like "status: 'some status message without encoding'".

Obviously, the object method is much simpler, and more importantly, it works. Did this change at some point?

from apps-script-oauth1.

The escaping behavior was changed in this commit. The problem I'm seeing now is that it's not checking to see if escaping is already disabled, in which case I shouldn't be escaping it again. I'll make a change to fix that.

from apps-script-oauth1.

Cool; that makes sense! Thanks.

from apps-script-oauth1.