@drewverlee because of performance. Any lookup for the potential query-string would waste CPU in all cases and for example in ring request routing, it’s never there according to the spec. There could be a variant of the function, parsing both path and the query-string, like there is reitit.frontend/match-by-path for the frontend.

Just pushed out reitit 0.4.0. It contains a couple of minor breaking changes – most likely they don't affect you but check out the changelog: https://github.com/metosin/reitit/blob/master/CHANGELOG.md#040