Anyone here doing coercion? Pedestal has regex constraints, but there is no built-in type coercion.
I generally feel that type coercion should be left to the request handler / terminal interceptor. If you need/have richer types (e.g. edn on the other end of the wire) then use a data format that supports it (e.g. transit).
Yeah, maybe you’re right. This is just for the basic routes, though. I think I’ll just do a CLJC namespace with some explicit regex and fns for casting that I can reuse.
Jetty CVE-2024-6763, a problem in all versions >=7.0.0, is fixed only in Jetty 12? https://nvd.nist.gov/vuln/detail/CVE-2024-6763 links to https://github.com/jetty/jetty.project/security/advisories/GHSA-qh8g-58pp-2wxh