Allow regexp for interceptor specs.

[jamestalmage]

Due to the high occurrence of / in paths, most people will probably use the string constructor form.

  scope.get(new Regexp("/somePath[a-z0-9]+")).reply(/** **/);

[sindresorhus]

👍 I think .get() should support both a regex and a function. This matches the filtering methods.

[ericsaboia]

+1

[hyzhak]

👍 definitely it will be great to have function in scope.get that be able to generate body of reply based on parsed path.

Something like this:

scope.get(function(url) {
   if(match(url)) {
      return {
        code: 200,
        body: generateBody(url)
      };
   } else {
      //it does not handle url
      return null;
   }
});

or that way

scope
  .get(function(url) {
    return match(url);
  })
  .reply(function(url) {
     return generateBody(url);
  });

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We try to do our best, but nock is maintained by volunteers and there is only so much we can do at a time. Thank you for your contributions.

[mastermatt]

Should this issue be open?
The features were added and still exist. tests

[RichardLitt]

Looks like it works for me. @jamestalmage @sindresorhus does this match your needs?

[sindresorhus]

Yes, thanks. For context, it was added in c303122.

[RichardLitt]

Awesome. Thanks for raising this, @mastermatt. All, this should be fixed now.