Fork me on GitHub
#yada
<
2017-01-15
>
geek-draven21:01:46

Hi, I've finally got around to learning Yada, as I'm about to start working on a pretty big web application, and decided I should start it with something more robust than composure as there are likely to be at least hundreds of concurrent users firing off api requests, and I'm going to need to restrict some areas based on user permissions. I've spent the weekend reading the Yada manual and I think I have a handle on it, but was wondering if anyone can recommend any online tutorials - I did start going through edge, but I'm used to having a project.clj, so got a bit lost. Something that starts with a blank sheet would be good - I'm trying to learn it at the moment by rewriting all my routes in an existing project. Thanks Ben

dominicm21:01:18

@geek-draven did you read build.boot much? The set-env! should feel familiar coming from lein.

geek-draven21:01:04

@dominicm I haven't used boot before, I had a quick look at the docs when I installed it to build edge. I use lein uberjar to build my projects

dominicm22:01:34

@geek-draven for the most part, it's the same, especially if you don't need to tweak anything. The build.boot in edge is a bit of a labour of love and has grown to have many handy but largely unnecessary features in. You can get by simply using boot dev and boot uberjar. Adding new deps can be done in the set-env! which is exactly like the one from leiningen.

geek-draven22:01:35

@dominicm Thanks, I'll take another look at it

naartjie22:01:39

Is there a way to make the request body optional? I'm getting tripped up by this line: https://github.com/juxt/yada/blob/d591f9fc0b470acfa2a52cbff5d0d3b21f497e36/src/yada/interceptors.clj#L187 It seems if {:parameters {:body ...}} is set to anything then the body is always expected. If I don't set {:parameters {:body ...}} then it's not being parsed at all.