are there any examples of large projects that are based on yada ?

it depends what you mean by large - http://juxt.pro runs off yada pretty much exclusively - @mccraigmccraig has a largish project in production, there are others

but yada is a new library, relatively speaking, so doesn't have anywhere near the footprint of Liberator and Pedestal

as malcolm said, my project uses yada for it's api - i'm happy to answer any questions you have @lmergen

ok, thanks

i'm the kind of person who always lurks a lot of other big projects to get some inspiration

edge helps a lot in this regard, though

is it correct that yada projects are usually small enough that a separate routes/ directory / namespace makes no sense ?

If you have a really big project, I would suggest separating routes out into each module and composing them together into a single route structure. Having one big route structure in a project would become a kind of 'god object' eventually

compojure/bidi/pedestal purposely supports this kind of recursive composition

data is so easy to compose, that's part of its attractoin

ok, good

furthermore, what is the best approach to testing yada ? just use the same test tools as you would use for testing a ring app ?

response-for, for example, only returns the body as a string, you have to manually coerce it

@lmergen: YMMV but I use 2 layers of tests - unit tests against my business usecases which don't include yada at all and api integration tests that fire up the server using the dev namespace and use clj-http to perform the actual http queries against it

using these I can test drive just about anything and as most of my tests go directly against the domain I get good execution times

right

that was the approach i was going to take

thanks!

https://github.com/juxt/modular

how up to date is the yada base structure there ? should i be using edge instead ?

I'd suggest edge.

ok