You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
@weavejester:uri would provide the full parsed path. For example instead of providing me with /nested/:greeting/world it would provide /nested/hello/world.
Ah, apologies, I misread and you're right that this isn't currently supported. I would be fine with a PR that adds a :compojure/full-route key to the request map.
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:
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.
The text was updated successfully, but these errors were encountered: