Clojurians Log v2

Maybe an obvious question, but how do I redirect SPA routing of all non /api urls for an app that is served using ring-reitit? On Netlify, this is achieved using a _redirects file (`/* /index.html 200`), but for this case I guess I need to create a route?

@love.lagerkvist you should use either a default handler (https://cljdoc.org/d/metosin/reitit/0.5.10/doc/ring/default-handler) or add a catch-all route in the route tree, e.g. ["/*" {:get index-handler}]

So I got reitit+malli working nicely for browser routing, coercing path params into proper values. Now I want to coerce the other way, encoding my values into url strings again. (reitit-frontend/match-by-path routes path) does the job for string->parsed-value, what is the best practice in the other direction? Do I use (m/encode …) directly on the path params?

Not sure this is the place for this question, but I am using reitit with the jetty adapter. I start the server straight from the repl. The question is, is there a debug mode that shows stack traces when the code returns a code 500?

Nevermind, the response contains the stack... my bad! Though it has the jetty stack that happens when the handler returns nil.

I have another question (I am not sure it is about reitit or jetty) but I created thre tests that basically make a single select in a Cassandra database, the difference between them is that the first was a synchronous ring handler, the second an async one and the third was an async handler using the async mode of the clojure Cassandra lib Alia. The thing is all 3 of them got the same performance (about 2000 req/s in my machine). Can anyone help me understand why there was no difference in performance? Does reitit or jetty automatically handle it somehow?

To be clear, I would be running this code:

(reitit-frontend/match-by-name routes :view {:tags #{:x :y :z}})

Expecting this output path:

"/view/x-y-z"