fix #380: allow any string to be servers variables

[xg1990]

According to the OpenAPI 3.0 specification, we should be able to use any variables in servers. More comments can be found in this issue: #380

This change is based on the latest documentation of path-to-regexp that we can specify the pattern of each path parameters

[xg1990]

This might also fix #113

[cdimascio]

thanks for the issue and the PR @xg1990. much appreciated.

i see. so looks like the current regex is not allowing you to have /s in the variable name. am i understanding this correctly?

with your new change, we'll end up with simple paths looking similar to the following

// given the path 'http://example.com/test/{me}/hello/{there}'

> urlPath.replace(/{(\w+)}/g, (substring, p1) => `:${p1}(.*)`)

// will now produce
'http://example.com/test/:me(.*)/hello/:there(.*)'

// rather than
'http://example.com/test/:me/hello/:there'

This seems reasonable. The new path matcher will have the same behavior as the previous logic, however we can now match the /s

Assuming, I'm understanding the issue correctly, your change looks reasonable to me

[xg1990]

Hi @cdimascio ,

Thanks for this response.

i see. so looks like the current regex is not allowing you to have /s in the variable name. am i understanding this correctly?

Yes, to be more precise, it's / in variable value

And your understanding is right, according to path-to-regexp 's documentation, if we have /:there(.*) then it will allow anything in the path

[cdimascio]

@all-contributors add @xg1990 for code

[allcontributors]

@cdimascio

I've put up a pull request to add @xg1990! 🎉

[cdimascio]

@xg1990 your fix is in v4.0.6