Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Can't access original request headers
See original GitHub issueWhat is the expected behavior? reply callback style should provide access to original request https://github.com/nock/nock#access-original-request-and-headers
What is the actual behavior?
requestBody is undefined in the callback. this is an empty object in the callback.
Possible solution I am pretty new to nock so am stumped…
How to reproduce the issue
Runkit: code with test case
Does the bug have a test case? Haven’t found one in nock master. Just in my runkit!
Versions
| Software | Version(s) |
|---|---|
| Nock | 10.0.1 |
| Node | 8.4.0 |
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
yeah I don’t like relying on
thiseither. Definitely something we should get rid ofThanks for the great bug report!
I’d start out by trying to create a failing test that reproduces your problem. Once you have that, start a pull request with the failing test. That would be a great start