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.
`removeInterceptor` with scope as an argument.
See original GitHub issueIt’s very easy to mistakenly pass a scope to removeInterceptor and not be aware it’s wrong.
First the difference between interceptor and scope is not explained at all in the README, as far as I can tell.
Second, after passing scope to removeInterceptor it actually returns true, even though it does not remove a single item. true is returned unconditionally here: https://github.com/node-nock/nock/blob/11f1a25ee88b0328c92070e4749793902907a60d/lib/intercept.js#L219 no matter if there was a single match in the inner loop just above it, or not.
It seems to me that passing a scope should just work, and be handled correctly (by removing all interceptor from the scope).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:5 (1 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
Thanks Adara for letting us know. We plan to invest some time to improve the documentation soon, so this is timely and valuable input 😃
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!