-
-
Notifications
You must be signed in to change notification settings - Fork 736
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
Is there a way to skip asserting the request body? #39
Comments
I ended up doing a match to
|
That's awesome. |
@jesusabdullah sorry, haven't been getting any emails on nock issues since I moved it to flatiron, even though I'm on the team :/ @jesusabdullah does this work for you or you think we should make it easier somehow? |
@pgte Actually that trick worked just fine! It might be nice to have it in the readme as a PROTIP or something but otherwise, yeah, I'm good. |
@jesusabdullah good advise, thanks, updated README. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue and add a reference to this one if it’s related. Thank you! |
I was working on the new jitsu tests (nock is fabulous for this btw), and I came across an interesting situation when trying to mock snapshot uploads here:
https://github.com/nodejitsu/jitsu/blob/flatiron-apps-tests/test/commands/apps-test.js#L99
What happens here is that jitsu tries to post a snapshot using content-type chunked, and for the life of me I can't figure out how to specify a request body in such a way that nock is cool with it.
You can see some of the errors I was getting here:
https://gist.github.com/39d0e24897c8d339722a
The easiest thing for me would be to tell nock to accept any request body, but if I can figure out how to make it handle a chunked body (copy-pasting the string-encoded .tgz didn't help) I'd be happy with that as well.
Any ideas?
The text was updated successfully, but these errors were encountered: