@ddeaguiar thanks a lot for the info. I would love to know how you unit test route without stubbing? Actually, in my case I use with-redefs to redefine a function.

@nxqd I typically test my routes in the context of an integration test. If I’m understanding your question correctly, you are trying to that your routes match incoming requests. To test route matching, you don’t need to use all the machinery provided by response-for, you can test against a router implementation directly. There are a number of ways to do this and I’ll share a gist shortly which illustrates them.

@nxqd https://gist.github.com/ddeaguiar/bed92b8f34b7e93f15cd0e5548d783ae

does any one used pedestal's logging library ? is it any good ?

There are things I like about it and things I don’t

can you share your experience with me please ?

I'm trying to choose between timbre, pedestal.log and logback

@donaldball ^

Requiring inline keyvals for everything is a little annoying particularly if you have the log data in a map already, and configuration is always more than a little hit or miss. Given my druthers, I’ll use unilog to configure logback and call it a day, but in a pedestal project I’ll bow to convention and use its logger.

@donaldball can i use it as slf4j backend ?