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
allowUnmocked: true + regexp host = interception fail #1076
Comments
Confirmed, here is a test case: https://runkit.com/gr2m/5a95927a75f2bb00122ffe55 Wanna send a pull request? Even just a test case reproducing the problem would already be helpful :) |
I am working on a PR for this issue. |
PR for the issue #1179 |
🎉 This issue has been resolved in version 9.4.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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! |
Similar to #1034, using regex in the host with
allowUnmocked = true
, fails to intercept.note: using version 9.2.2
The text was updated successfully, but these errors were encountered: