Changelog for dhall-yaml-1.2.12
- Build against
dhall-1.42
1.2.11
- Add new
--preserve-headeroption - Builds against newer dependencies
1.2.10
- Build against
dhall-1.41 - Build against
optparse-applicative-0.17 - Build against
text-2.0
1.2.9
1.2.8
- Build against
dhall-1.40.0
1.2.7
- Build against
dhall-1.39.0
1.2.6
1.2.5
- Build against
dhall-1.38.0,tasty-1.4, andtasty-silver-3.2
1.2.4
- Build against
dhall-1.37.0
1.2.3
1.2.2
1.2.1
- Format documents with leading
---- Now if you use the
--documentsflag the first document will also include a leading---
- Now if you use the
1.2.0
- BREAKING CHANGE: Add
--generated-commentflag fordhall-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
noEditfield to the options type - In practice this breakage won't affect most users
- Produce output compatible with YAML 1.1
- Special strings like
onare now quoted in order to avoid being misinterpreted as boolean values by YAML 1.1 implementations
- Special strings like
- 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-dhallsupport 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
schemafield of theOptionstype now has typeMaybe Textinstead ofText
- Add
yaml-to-dhall typesubcommand- 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-dhallsupport for usingtoMap- Now if you specify a
Mapas the schema, the generated Dhall code will usetoMapto improve the appearance
- Now if you specify a
1.0.3
1.0.2
- Build against
dhall-1.30.0
1.0.1
- Build against
dhall-1.29.0
1.0.0
- Initial release