Allow escaping so that a literal ":" can be used in a route.

[brianedgerton]

Use Case
I'm trying to create an OPTIONS endpoint that returns some API documentation with a url like:

/api/posts/:post/comments/:comment

No matter what I do, I can't escape the colons to prevent them from being turned into the catch-all regexps in the router.

Code
I've tracked the route string transformation all the way down to regifyString() in /lib/director/router.js. It would seem that the parsing there needs to be slightly changed. If this would be a welcomed change, I can work on a PR.

Thanks!
Brian Edgerton

[edef1c]

:: may be a nice syntax.

[brianedgerton]

A syntax for escaping or for use in the URL? As it stands currently, /::post_id would still result in the regexp substitution. I tried that in my quest to get it to escape :)

[edef1c]

Yeah, just my proposed syntax. It seems reasonably unambiguous to me.

[brianedgerton]

Ok, I'll play around with the code a little bit. Just so we're clear on the expectation, declaring a route like this:

/api/posts/::post/comments/::comment

Would produce a literal url like this:

/api/posts/:post/comments/:comment

Sound right?

[edef1c]

Yep.

[brianedgerton]

@nathan7 I've submitted a PR with tests added to test/server/core/regifystring-test.js. Everything is passing.