How come yada/response-for is only used for tests, and not the implementation itself?

Reason I’m asking is that I’m testing a cljs-implementation of (very small parts of) yada, and I’m seeing small differences when testing against a running instance of yada/aleph and response-for.

Differences being {:body ""} vs {:body nil} and json vs edn output when requesting with accept: application/json

Hmm. That's a bug. The response-for should run the whole chain so shouldn't be differences.

Ok!

Also seing a 406 from the server and a 200 from response-for when sending a non-acceptable accept header