Removed JSON.stringify to prevent double stringify

[iameugenejo]

requestjs applies JSON.stringify to the request body when json option is true. Stringifying from this module makes the requestjs to send request body as "{}" instead of {} making the server throw "invalid json" when bodyparser module is used.

I just removed JSON.stringify in this module to fix the issue.

[vlucas]

This was due to bug in upstream Request library: request/request#1313

Update to Frisby v0.8.4 for fix.

[HugoSousa]

I have Frisby v0.8.4 installed and actually got this problem too. Only saw this after creating a new issue (#172).

The change seems to have fixed my problem too.

[bkhurshi]

This issue does not seem to have been resolved in v0.8.4.
I created the following simple test:

frisby.create("Do something")
    .post('http://localhost:8529/_db/fiplus/dev/extensions/thing',
    {
        thing: "blah"
    }, {json: true})
    .inspectJSON()
    .toss();

with extensions/thing simply echoing the body of the request back in the response. I get the following error:

   Message:
     Error: Error parsing JSON string: Unexpected token o
        Given: [object Object]

The stacktrace points to frisby.js:1218:11

[ecowden]

Is there any way to get a new release now that this is merged in? 😁

It looks like this change is not in v0.8.4, so all of our tests which do POSTs continue failing.

Thanks in advance!

[JoyShafer]

I'm new to coding in general and brand new to Frisby. I've been pulling my hair out for several weeks trying to figure out why none of my post requests were working. I've implemented a fix locally and can finally see my tests passing. Yay!
Can you wrap the official fix into a new installable Frisby package, please?

[vlucas]

Just published v0.8.5 which should fix this.

[ecowden]

Thanks @vlucas! Works great!

[JoyShafer]

Yes, thank you. The v0.8.5 is working for me.