Router doesn't match URLs with query params

[calebfaruki]

This could be patched on mainframe codebase with regex that capture query params, but it's annoying because most browsers don't support positive lookaheads/lookbehinds. Haven't found a suitable hack for this yet.

Solution would be to drop query params from router before the match and pass to view after route match.

[calebfaruki]

Regex attempted but result in various RegExp issues.

^\/projects\/([a-z0-9]+)\??.*$ // captures, but no id or params passed to view.
^\/projects\/([a-z0-9]+)[/]*(\?.+)*$ // invalid capture group.

Test cases

/projects // shouldn't match
/projects/ // shouldn't match
/projects/fdsafdsa // should match
/projects/fdsafdsa/ // should match
/projects/fdsafdsa/download // shouldn't match
/projects/fdsafdsa?phase_id=fdsafdsa // should match
/projects/069fdb4a44b84013bca0f0f59ae9a718?phase_id=7776ca11567e4b8093217bd110d20b79 // should match
/projects/fdsafdsa/?phase_id=fdsafdsa/ // should match
/projects/fdsafdsa?phase_id=fdsafdsa/ // should match

[malomalo]

I think this currently works with this as the route '/projects/:id', but manual regexes do match against the query string. I think we should remove that too... @bemky what do you think?