Clojurians Log v2

@weavejester Yes this is by design. Right now, Reitit only considers the leaf nodes on the route tree for endpoints. There is no logic which can choose if a non-leaf node should be considered a endpoint or not. (I think there is some logic for match-by-name for choose endpoints based on if the route-data has :name or such.) (I think we did consider adding a option which could do this, so user could check for :name or :handler or whatever they use.)

To clarify the issue, when I check the routes manually everything works, but when I add coercion and middleware, nested routes aren't processed. There's clearly something going wrong somewhere, but it's all very opaque. Ideally I'd like Reitit to report back on why the router hasn't matched a route.

I think I've tracked down the issue by going through the configuration and middleware piece by piece. It's no fault of Reitit's, but the lack of transparency once the router was built made it hard to figure out the exact component that was going wrong. I'm unsure of the best way to address this, however.

What was the problem?

Some code altered the routes in an unexpected way, so the routes I was looking at weren't the routes passed into the router.

So when I tested the routes by passing them directly to the router in the REPL they worked, but when the server started they didn't. It was very confusing until I realised the issue.

Depending on what you're doing of course, but if you have :name on your routes, then you can match-by-name and check what the final result (with all the :data and :middleware and whatnot) looks like Even without :name you should be able to match-by-path to see if the issue is in the router or somewhere outside of it I don't know if there is a function to list all routes in a router

Calling reitit.core/routes on router returns the flattened route tree. I can be useful in debugging.

That's super helpful, because I don't seem to have fixed the issue, and I've added some debugging right before the router is constructed so I know the routes are all correct. Hopefully I can figure out just what's going wrong if I poke it enough.

Ahh, I see. I've misunderstood the syntax. I had assumed that:

["/foo" {:name :foo} ["/bar" {:name :bar}]]

["/foo" ["" {:name :foo}] ["/bar" {:name :bar}]]

(Incidentally, that tip about reitit.core/routes saved me a lot of time)