allowUnmocked option doesn't work properly for specified paths

[sidx1024]

What is the expected behavior?
Specified path predicate + allowUnmocked doesn't return mocked response.

What is the actual behavior?
Specified path predicate + allowUnmocked should return mocked response.

Possible solution

How to reproduce the issue

test('match path using regexp with allowUnmocked', function (t) {
  nock('http://www.test-domain.com', {allowUnmocked: true})
    .get(uri => uri.endsWith('predicate'))
    .reply(200, 'Matched predicate');

  axios.get('http://www.test-domain.com/resources/predicate', function(err, res, body) {
    t.type(err, 'null');
    t.equal(res.statusCode, 200);
    t.equal(body, 'Matched predicate');
    t.end();
  });
});

Runkit: Example link

Having problem producing a test case? Try and ask the community for help. If the test case cannot be reproduced, the Nock community might not be able to help you.

Does the bug have a test case?

Versions

Software	Version(s)
Nock	11.7.2
Node	12.4.1
TypeScript

[mastermatt]

From a first look on trying to recreate this, it seem to only be broken when the verb method is provided a callback. Passing a string or regex works as expected.
I'm going to keep looking.

[nockbot]

🎉 This issue has been resolved in version 11.8.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀