dhall-yaml

Note that the dhall-json package also provides a dhall-to-yaml executable. Currently, the behavior of the dhall-to-yaml and dhall-to-yaml-ng executables should not differ much, but eventually the dhall-to-yaml-ng executable should be able to support greater functionality due to using the HsYAML package as an intermediate step in the transformation process.

Tutorials for the analogous JSON tools are available in the dhall-json package:

Example

$ dhall-to-yaml-ng <<< "{ foo = [1, 2, 3], bar = { baz = True } }" > example.yaml
$ cat example.yaml
bar:
  baz: true
foo:
- 1
- 2
- 3
$ yaml-to-dhall '{ foo : List Natural, bar : { baz : Bool } }' < example.yaml
{ bar = { baz = True }, foo = [ 1, 2, 3 ] }

Changes

Build against dhall-1.42

1.2.11

Add new --preserve-header option
Builds against newer dependencies
- aeson-2.1

1.2.10

Build against dhall-1.41
Build against optparse-applicative-0.17
Build against text-2.0

1.2.9

Build against aeson-2.0

1.2.8

Build against dhall-1.40.0

1.2.7

Build against dhall-1.39.0

1.2.6

Allow bytestring-0.11

1.2.5

Build against dhall-1.38.0, tasty-1.4, and tasty-silver-3.2

1.2.4

Build against dhall-1.37.0

1.2.3

Fix command-line completions for files

1.2.2

The --documents flag now wraps non-Lists in a document

1.2.1

Format documents with leading ---
- Now if you use the --documents flag the first document will also include a leading ---

1.2.0

BREAKING CHANGE: Add --generated-comment flag for dhall-to-yaml{-ng}
- You can now optionally add a comment header to the YAML output indicating that the file is generated and should not be hand-edited
- This is a breaking change because this adds a new noEdit field to the options type
- In practice this breakage won’t affect most users
Produce output compatible with YAML 1.1
- Special strings like on are now quoted in order to avoid being misinterpreted as boolean values by YAML 1.1 implementations
Show JSON/YAML path on error reporting
- Error messages will now include the path to the error in the diagnostic output

1.1.0

BREAKING CHANGE: Add yaml-to-dhall support for inferring the schema
- You no longer need to provide the command with an explicit schema. The command will infer a reasonably close schema from the provided YAML
- This is a breaking change because the schema field of the Options type now has type Maybe Text instead of Text
Add yaml-to-dhall type subcommand
- You can use this subcommand to print the inferred schema for a YAML value, so that you can edit the schema and use it for subsequent invocations.
Add yaml-to-dhall support for using toMap
- Now if you specify a Map as the schema, the generated Dhall code will use toMap to improve the appearance

1.0.3

yaml: Single-quote date/bool string fields

1.0.2

Build against dhall-1.30.0

1.0.1

Build against dhall-1.29.0

1.0.0

Initial release