Hello. I'm using reitit 2.7. I'm trying to create nested path with handlers. Can't understand why all intermediate handlers are ignored?

I can invoke only "/test1/test2" handler. Why I can't invoke "/test1" handler?

@mike1452 handlers are request => response functions, so you can compose them. You should use Interceptors for that, as all the steps are context => ->context, so you can chain them.

@ikitommi A, thanks. Now I understand the logic.

behind the scenes, all intermediate data is meta-merged into endpoints: Interceptors are defined in vector, and thet get conjoined. handlers are defined as functions, so the last one wins

but anyway I've achieved desired behaviour by this code.

you can ask the merged final route tree (with data) from the router to see how it looks

Oh, there was a discussion to allow the intermediate paths with handlers to function as endpoints too. Can't remember how it ended. If you wish this, please write an issue.

here is a full example. now, i have handlers on any level, all intermediate interceptors are executed.

@mike1452 wrote https://github.com/metosin/reitit/issues/175 for this.

also, copied from c-api the new spec error handling: the spec problems will be available in the error handlers, so one can plug in expound, pinpointer or any other spec pretty printer to handle spec errors.

has anyone else had this bug where the body editor part of the Swagger-UI doesn't render?

I'm trying to migrate from compojure-api to reitit 0.2.7 and all I see is:

https://pasteboard.co/HNCVn9p.png

@robert.mather.rmm have you defined both :coercion and :parameters &/ :responses?

:coercion under :data in the top-level ring/router, only :parameters at the leaf/handler

sounds legit. there is a working example in https://github.com/metosin/reitit/blob/master/examples/ring-swagger/src/example/server.clj. hope this helps, going offline now.

k, thanks. That's what I've been following. I'll keep poking around