.forMethod() and .forPath() new matchers proposition

[OnkelTem]

Currently if you need to match an URL, you have to use one of the method-specific matchers: forGet(), forPost(), etc. But when you need to match a URL for some of the HTTP methods, you have to repeat yourself:

server.forGet(url)//...;
server.forPost(url)//...;
server.forOptions(url)//...;
server.forHead(url)//...;
// etc

I propose to add 2 new methods:

• forMethod(method) matcher, which is true when method matches the current method

enum HttpMethods {
  CONNECT = 'CONNECT',
  DELETE = 'DELETE',
  GET = 'GET',
  HEAD = 'HEAD',
  OPTIONS = 'OPTIONS',
  PATCH = 'PATCH',
  POST = 'POST',
  PUT = 'PUT',
  TRACE = 'TRACE',
}

forMethod(method: HttpMethods): RequestRuleBuilder

• forPath(path) - matcher which is true when path matches the current requested path.

forPath(path: string | RegExp): this;

[pimterry]

Sure! PRs welcome. This should be very quick & easy since the matchers already exist for internal use (defined here and here), it's just that it's not exposed in the rule builder API.

[OnkelTem]

Yep!