Fork me on GitHub

@ordnungswidrig As nearly all my resources need a JSON representation, and many of them use UUIDs, I'll be adding this same :as-response workaround over and over. I'll also have to handle the other representations (eg, EDN) even though I want liberator's default behavior there. Is there another pattern I could adopt?


The support for UUID in cheshire vs. non-support in (and no documentation on how to extend its encoding/decoding) make me see much more clearly the value proposition of using it instead -- have you considered that?