[web-devel] when we switch to aeson, perhaps a QQ for JSON..
greg at gregweber.info
Thu Mar 17 15:01:32 CET 2011
I agree that ToJson as is now is biased towards arrays. I have some code
like the below now. After we switch over we should make sure it is easy to
create key-value objects. Perhaps we will need a second ToJson that is
biased towards key-value objects instead of arrays.
documentToJson :: [Field] -> J.Value
documentToJson = jsonMap . map toAssoc
toAssoc :: Field -> (String, J.Value)
toAssoc (l := v) = (unpack l, toJson v)
On Wed, Mar 16, 2011 at 11:44 PM, Max Cantor <mxcantor at gmail.com> wrote:
> ToJson doesn't seem to be able to generate JSON objects (key/value maps).
> Also, one problem that I've had with other generic JSON libs is that they
> dont give you enough control over the JSON structure. So, you need to write
> your client code around a particular JSON structure which can be unwieldy at
> On Mar 17, 2011, at 1:37 PM, Greg Weber wrote:
> > Are you using the ToJson converter? I don't think QQ offers much
> advantage over utilities that can automatically convert haskell data
> structures to JSON. I believe aeson comes with this functionality and also
> some generics functionality if you define a Data instance.
> > On Wed, Mar 16, 2011 at 8:32 PM, Max Cantor <mxcantor at gmail.com> wrote:
> > I know that the kickass yesod team is looking to change the json library
> to aeson.
> > One nice feature would be quasi-quoting for the library like in the
> following library.
> > _______________________________________________
> > web-devel mailing list
> > web-devel at haskell.org
> > http://www.haskell.org/mailman/listinfo/web-devel
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the web-devel