When extracting a route path using (:compojure/route req) we can retrieve the raw unparsed path. So for example if my path is /hello/:name and a user hits /hello/world, I can retrieve /hello/:name. This is extremely useful for tracing and to capture metrics in general.
Now the issue is that this isn't (doesn't seem?) doable when using a context. For example, given this context:
(context "/nested/:greeting" [_]
(GET "/world" [_] {:status 200}))If a user hits /nested/hello/world, we can retreive /nested/hello from the request (in the :context), but not /nested/:greeting.
Our goal is to have the /nested/:greeting/world string available for our telemetry data.
It would be amazing if this could be supported.
When extracting a route path using
(:compojure/route req)we can retrieve the raw unparsed path. So for example if my path is/hello/:nameand a user hits/hello/world, I can retrieve/hello/:name. This is extremely useful for tracing and to capture metrics in general.Now the issue is that this isn't (doesn't seem?) doable when using a context. For example, given this context:
If a user hits
/nested/hello/world, we can retreive/nested/hellofrom the request (in the:context), but not/nested/:greeting.Our goal is to have the
/nested/:greeting/worldstring available for our telemetry data.It would be amazing if this could be supported.