The generic-aeson package

[Tags: bsd3, library]

Derivation of Aeson instances using GHC generics.


[Skip to ReadMe]

Properties

Versions0.1, 0.1.0.1, 0.1.0.2, 0.1.0.3, 0.1.1, 0.1.1.1, 0.2.0.0, 0.2.0.1, 0.2.0.2, 0.2.0.3, 0.2.0.4, 0.2.0.5, 0.2.0.6, 0.2.0.7
Change logCHANGELOG.md
Dependenciesaeson (>=0.6 && <0.10), attoparsec (>=0.11 && <0.14), base (>=4.4 && <4.9), generic-deriving (>=1.6 && <1.9), 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.12) [details]
LicenseBSD3
AuthorSilk
Maintainercode@silk.co
CategoryData
Source repositoryhead: git clone https://github.com/silkapp/generic-aeson.git
UploadedTue Jun 30 05:39:56 UTC 2015 by AdamBergmark
UpdatedTue Jul 14 15:27:27 UTC 2015 by ErikHesselink to revision 1
DistributionsLTSHaskell:0.2.0.7, NixOS:0.2.0.7, Stackage:0.2.0.7
Downloads3534 total (371 in last 30 days)
Votes
0 []
StatusDocs available [build log]
Last success reported on 2015-06-30 [all 1 reports]

Modules

[Index]

Downloads

Maintainers' corner

For package maintainers and hackage trustees

Readme for generic-aeson-0.2.0.7

generic-aeson

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.

Schemas

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