add workaround to fix changed route based on regular expression while…

[s-a]

Currently the initialization process seems to change routes based on RegEx. I do not expect that you will accept this PR. It is intended to point out the problematic code. I think this code change is only a workaround for #1581 because from my point of view we should not change the initial regular expression passed to .getmethod where

/\bv?(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)(?:-[\da-z-]+(?:\.[\da-z-]+)*)?(?:\+[\da-z-]+(?:\.[\da-z-]+)*)?\/?.*\b/ changes to
/\bv?(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)(?:-[\da-z-]+(?:\.[\da-z-]+)*)?(?:\+[\da-z-]+(?:\.[\da-z-]+)*)?\/?.*\b/gi. I am not a RegExpert but I think this should not make a difference and it changes back to original RegEx at runtime but it leads to fail matchURL

Pre-Submission Checklist

• Opened an issue discussing these changes before opening the PR
• Ran the linter and tests via make prepush
• Included comprehensive and convincing tests for changes

Issues

Closes:

• Issue .get does not identify valid route request after it returned correct response #1581

[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. Thank you for your contributions.

[stale]

This issue has been automatically closed as stale because it has not had recent activity.