The structure of the generated JSON is meant to be close to idiomatic JSON. This means:
Enumerations (data types containing constructors without fields) are converted to JSON strings.
Record fields become JSON keys.
Data types with one unlabeled field convert to just that field.
Data types with multiple unlabeled fields become arrays.
Multiple constructors are represented by keys.
Maybevalues are either an absent key, or the value.
Leading and trailing underscores are removed from constructor names and record fields
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.
- Fix a documentation typo
- Fix compilation on GHC 8.
- Fix compilation on GHC 7.4
gparseJsonWithSettingsto customize the generated JSON, currently only to strip specified prefixes from record fields.
- Format Change: The behavior of Maybes was inconsistent and buggy,
now we always map
Justdirectly to the value, and
Nothingto null if on the top level or in an unnamed field and remove the property if it’s in a named field.
- Changed the type of
selNameTto return a
Maybe Textwhich will be
- Fix regression in implementation of
multipleConstructorsintroduced in 0.1.1
Generics.Generic.Aeson.Utilmodule with helper function for interoperating packages