generic-aeson: Derivation of Aeson instances using GHC generics.

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.



Derivation of Aeson instances using GHC generics.

[Skip to ReadMe]


Versions0.1,,,, 0.1.1,,,,,,,,,,,,
Dependenciesaeson (>=0.6 && <1.3), attoparsec (>=0.11 && <0.14), base (>=4.4 && <4.10), generic-deriving (>=1.6 && <1.12), ghc-prim, mtl (>=2.0 && <2.3), tagged (>=0.2 && <0.9), text (>=0.11 && <1.3), unordered-containers (==0.2.*), vector (>=0.10 && <0.13) [details]
Source repositoryhead: git clone
UploadedSun Apr 23 11:02:46 UTC 2017 by AdamBergmark




Maintainers' corner

For package maintainers and hackage trustees

Readme for generic-aeson-

[back to package description]


Build Status

The structure of the generated JSON is meant to be close to idiomatic JSON. This means:

See tests/Main.hs in json-schema for more examples.

How does generic-aeson compare to the TH/Generics already present in aeson?

generic-aeson contains more special cases for creating more concise and idiomatic json. If you're working with the JSON representation directly generic-aeson should feel more natural.

Will the generated format ever change?

Changing the format would incur a breaking change to every API that uses generic-aeson so we must keep it intact.

If we find a bug where the fix changes the format we need to create a new package or version the generation code.


json-schema has generic derivation of schemas that match the generic-aeson format.