I just did something similar with component, maybe you could steal ideas?

I can have a looksee, but from what I've been playing around, I have to reload the system so far

do you have a link?

no, but I can tell you what I did Order of dependencies for components: server -> ring-handler -> ring-router -> routes -> handlers map routes: [[path-a handler-a] ... Then in development you can pass all the handlers as vars instead of function values, or build the handlers wrapped in (fn [x] (handler x)) making sure they are referenced by name and not by value at dev time also see https://github.com/metosin/reitit/blob/master/doc/advanced/dev_workflow.md#an-easy-fix

Yup, thank you. Reading that, so far, can't get it to work. Will keep plugging away at it.

I got it wrong for about three hours until I figured it out

WHen you say referenced by name, not value, can you elaborate?

One way to do it is with vars, another is requiring resolve, or (fn [x] (f x)), which doesn't do anything, but is compiled in a way where f isn't passed by value

kk

Something like (defmacro $ [f] (fn [~'x] (~f ~'x))) then when you refer to your handler which you pass to the routes do it with ($ handler)

checked it now, works as expected

thank you, will give it a whirl

Do you want to share a code snippet?

Sure, I'll DM you

figured out in the end that you can just concat on the end of the function call.