@dominicm: I've removed yada's matchers for bidi in the latest yada release. @stijn and I have discussed providing tree walkers that will do the necessary transformations from plain maps (representing resource models) and yada handlers, with an option to alter the resource models along the way. Removing yada's bidi matching on maps at request time is in preparation for this - and I think the fact that yada extended bidi's protocols is a little surprising for users (violates the principle of least surprise) - bidi protocols are already 'hard' and I don't want to make them harder to understand

all, sorry for the recent breakages while the beta process continues - the point is to try to remove the remaining kinks so that 1.1.0 final can be very stable for adoptees - thanks for your patience - @nha please let me know the yada version you've been having problems with - there's been a few releases lately

@jannis thanks for that PR

@jannis I'm not going to clojure d, but plan to next year

@malcolmsparks: Same here

I hope the falling back to octet stream change is reasonable. I noticed that otherwise serving resources with unknown mime types like JS source maps would fail.

Great, I will switch to the latest and greatest then

I am new to yada, coming from liberator, and I have a question on how to best implemented something in yada. In liberator I normally use a :unprocessable? method in liberator for errors when, for example, one some is trying to add an email to my system that already exists. In other words the request is correctly formatted but the values in that request are wrong or already taken. In order to do something like this I think i would need to write my own interceptor-chain

So, I have something like

So I have a couple of questions. Is this the right path? Should I be implementing my own interceptor chain? Where should I put this check in the chain?

thanks