This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-31
Channels
- # admin-announcements (1)
- # beginners (16)
- # boot (25)
- # braid-chat (7)
- # cider (4)
- # cljsfiddle (6)
- # cljsrn (1)
- # clojure (256)
- # clojure-austin (4)
- # clojure-ireland (1)
- # clojure-poland (15)
- # clojure-russia (80)
- # clojure-uk (2)
- # clojurescript (30)
- # core-async (14)
- # core-typed (3)
- # cursive (35)
- # datomic (1)
- # editors (28)
- # hoplon (32)
- # immutant (1)
- # jobs (8)
- # jobs-discuss (1)
- # juxt (6)
- # leiningen (8)
- # liberator (7)
- # off-topic (16)
- # om (69)
- # onyx (38)
- # re-frame (10)
- # spacemacs (1)
- # untangled (117)
@ordnungswidrig: I think I've found a small bug in liberator: https://github.com/clojure-liberator/liberator/issues/254 It's easily resolved and I can issue a PR if you'd like.
oh looks like this has been fixed already in 0.14.0
.... https://github.com/clojure-liberator/liberator/blob/master/src/liberator/core.clj#L563
I've closed the issue
sorry for the hassle
No worries, this is a rough edge of liberator.
When you try to combine custom as-response and ring-response to manipulate headers then you'll find yourself in even weirder terrain.
yeah I can imagine - I had some weirdness a while back with ring-response
- I can't remember the details - I might've been fighting against the grain of liberator though...