yada
yada copied to clipboard
juxt
A powerful Clojure web library, full HTTP, full async - see https://juxt.pro/yada/index.html
Is there any support or planned support for response schemas, similar to the current support for request parameter schemas? This would be helpful in swagger generation, and it would also...
For a resource that produces a media type of `application/json`, no response is rendered. I see that the JSON media type is commented out of the declarations in `yada.handler/error-representations` with...
https://github.com/juxt/yada/blob/master/src/yada/util.clj#L241 returns 0 for a partial function. This leads to an Arity error when requesting the resource.
I believe the below doc should refer to yada.handler/prepend-interceptor ```23.2. Modifying interceptor chains Say you want to modify the interceptor chain for a given resource. You might want to put...
Server 1: yada/aleph Server 2: yada/aleph Used in the following fashion : Server 1 Server 2 Browser When using server 2 [as a proxy](http://www.codegist.net/snippet/clojure/aleph-proxyclj_hiredman_clojure), the request's body becomes of class...
When upgrading to hiccup `2.0.0-alpha1`, `hiccup2.core/html` returns a RawString where previously it returned a String (I think?). This caused an error in Aleph: ``` 17:14:25.854 [aleph-netty-server-event-pool-12-2] ERROR aleph.http.core - error...
@danielcompton writes > I was printing out the ctx map in my handler and noticed that the `:known-methods` methods seem to create a new instance every time I reload the...
I think it might be a bug in yada where if you don't send an Accept header (which implies _/_), the Content-Type isn't set
``` PS C:\Users\ykomatsu\Documents\yada> lein test ... lein test :only yada.custom-error-response-test/custom-error-with-body FAIL in (custom-error-with-body) (custom_error_response_test.clj:97) GET custom error with response body [application/edn] expected: (= "{:message \"custom error message\"}\n" (b/to-string (:body response)))...
`%25` is `%` when url-decoded. Query params with this char in them will decode to nil, if used with `request-for`. Eg `/?foo=bar%25` results in `{"foo" nil}` instead of `{"foo" "bar%"}`...
