@ikitommi I like that router lib, it's well put together really

I d like it even more if it limited itself to routing tho. Shouldn't the coercion/middlware'intercept be a "resource" level concern?

maybe that's what you meant with separate artifacts tho

I think I might give it a try

@mpenet great to hear you like that! Agree that the simplest definition for a routing lib is just route definition & matching, e.g. reitit.core. Have to learn how to maintain a mono-/multirepo to be able deploy the layers as separate artefacts. Only dependency in the lib is meta-merge, so it has been easy to develop all in same repo/project.

not claiming this is the best way, but I do it one way that works for me on https://github.com/mpenet/alia

this one uses lein, but it s very similar (easier actually) with boot, that's what I use on internal stuff now

I guess it's kinda similar to the way ring is organized too