Naive regex builder that helps henerate url matchers for $httpBackend based on routing syntax.

$httpBackend-url-matcher-builder.coffee

# https://docs.angularjs.org/api/ngMockE2E/service/$httpBackend

### @usage
path = require './path'
urlMatcher = path '/users/:guid/helloworld/:guid'

phones = [{name: 'phone1'}, {name: 'phone2'}]

$httpBackend.whenGET(urlMatcher).respond(phones)

Most of the time you just want to match on the end of the url as opposed to the full url (host header + request path)
as base addresses typically change per environment. For example, instead of matching on https://github.com/armw4,
I'd write a matcher less brittle like /armw4$/ (only testing the end of the url, excluding the scheme,
host, port, etc.). So this will suffice.
###
placeHolders =
  guid: -> "[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}"

invokePlaceholderPipeline = (pattern) ->
  accumalatorValue = pattern

  for key, valueFactory of placeHolders
    keyReplacementRegex = new RegExp ":#{key}", 'g'

    accumalatorValue = accumalatorValue.replace keyReplacementRegex, valueFactory()

  accumalatorValue

path = (requestPath) ->
  forwardSlashesEscaped = requestPath.replace(/\//g, '\\/')

  urlSelectorPattern = invokePlaceholderPipeline forwardSlashesEscaped

  urlSelectorRegex = new RegExp urlSelectorPattern

module.exports = path

# sample code
actual = 'https://github.nreca.org/users/e887e740-31f2-4530-911e-4fec9be2cc45/helloworld/e887e740-31f2-4530-911e-4fec9be2cc45'

x = path '/users/:guid/helloworld/:guid'

console.log 'it"s a match mang' if x.test actual # it"s a match mang

Obviously if you were to use this in node land, you'd wanna compile the coffee file and do something like:

path = require('path/to/file/containing/url/matcher/function')

urlMatcher = path('/users/:guid/helloworld/:guid');

I would use this in conjunction with kbaltrinic/http-backend-proxy. In fact, that's exactly why I built it. I will probably look to integrate this into armw4/protractor-trials at some point just for display purposes. Holla...

Probably handy to escape ? too since it will be used for matchers containing query strings. Basically whatever you can do to make your paths more human readable then you should do it. Try to encapsulate escaping cuz it's just plain ugly and sucks. Ya digg??

Snippet to escape ?:

forwardSlashesEscaped = requestPath.replace(/\//g, '\\/').replace('?', '\\?')