Yes, you can do all sort of preprocessing with it. You should add your own rules to the default rules - if you find them usefull (e.g. use any coercion)

What is the rule that propagates information from higher levels to lower levels. e.g. if I have a route [“top-level” {:some-key true} [“/next-level” {:more :info}]] at what point does some-key make it into the next-level

Ideally I’d place a function after this is done, so I can use this info and expand on it.

Here's a short description of the full route expansion : there are several hooks available to change things: https://cljdoc.org/d/metosin/reitit/0.7.0-alpha5/doc/basics/router#behind-the-scenes

I think :compile is the one you are looking for. If you use ring, you should compose your code with the reitit-ring default compile. See source code for more info. And please share how and what you did

Yes, thanks, compile did the trick!

I used it for a whole bunch of things, one example was to merge in responses for the open api docs. e.g. 400 - incorrect and 500 - error responses, and if :allow-unauthenticated? key on the route is false, 401 - unauthorized and 403 - forbidden.

I tried this on my project, but it broke hot-reload. Anyone else experience that?

@UTFAPNRPT is it your project with lein-figwheel or shadows-cljs? bc i have the hotreload code feature working with shadow.

For me hot-reload works with shadow-cljs, but sometimes I have to refresh a browser page manually. I assume it's due to defonce .

@U1ZJ06MMK my project is shadow. I did some searching here in clojurians and it seems like others have experienced the issue as well. @U01320BR6US I have to refresh the page every time. That’s just not tenable. For now I’m back on 17.

This is great stuff. I never had an issue with my reitit fe router, at least, I never noticed it. I probably haven’t changed my route definitions much, and when I did, I must have just did a hard reload. This is good info to watch out for in future.