This module provide a way to generate Elm types, encoders, and decoders for json-spec Specifications

Generally you will probably want elmDefs, but sometimes you might want to directly use the methods of HasType.

Since not every part of a Specification may have a name, we can generate encoders and decoders for anonymous Elm types like records, as well as named Elm types and type aliases. This package figures out how to name things given the following rules:

• If a name appears in a JsonLet binding, then it gets a name in Elm as a type or type alias.
• If a second JsonLet binding, with exactly one definition, of the form JsonLet '[ '(name, def) ] (JsonRef name) appears as the RHS of a JsonLetbinding, then that is interpreted as a constructor name, and the generated Elm definition will be a regular type instead of a type alias. See Named for an easy shorthand way to spell JsonLet '[ '(name, def) ] (JsonRef name)
• For any Named leaf of a tree of JsonEithers, the name is interpreted as a data constructor name, otherwise a data constructor name is auto-generated.

Examples:

Type alias

The specification

Named "MyType" JsonString

will produce the Elm type

type alias MyType = String

Type with a constructor

The specification

Named "MyType" (Named "MyDataConstructor" JsonString)

will produce the Elm type

type MyType = MyDataConstructor String

Sum Type

Note that the root of a tree of JsonEithers must be named, because Elm has no way to represent anonymous sum types.

The specification

Named "MySumType"
  ( JsonEither
      (Named "AnInt" JsonInt)
      ( JsonEither
          JsonFloat -- note the omitted name
          ( Named "AString" JsonString)
      )
  )

will produce the Elm type

type MySumType
  = AnInt Int
  | MySumType_2 Float -- auto-generated constructor name.
  | AString String

Producing actual Elm code

This package gets you as far as having a collection of Definitions in hand, which come from the 'elm-syntax' package. You will need to use the pretty printing features of that package to actually produce code. See https://hackage.haskell.org/package/elm-syntax/docs/Language-Elm-Pretty.html, or you can look at the source code for the tests in this package.