Release v0.2.0 · VirtusLab/scala-yaml

What's Changed

Fixed a bug (#314) where decoding as Any lost precision due to preference of Float over Double. Side effect of this change is that this is a breaking change as all decimal numbers in range of double precision will be parsed as Double instead of Float.
Fixed a bug (#313) where an ellipsis was parsed as a document end marker even when it was a part of a value in a mapping.
Fixed a bug (#281) where newlines were escaped in literal scalar blocks.
Fixed a bug (#258) where backslashes were escaped in single-quoted strings.
Fixed a build configuration bug (#228) which caused publishing of scaladocs for integration tests module.
Fixed a bug (#222) where some valid numeric values were not parsed as numeric types.
Fixed a bug (#216) where non-printable characters were not escaped into their readable form when printing yaml.
Provided an improved error message for #120 which occurs when a !!null tag is encountered where a non-optional type is expected in target structure.
Fixed a bug (#86) where mapping without a value was not parsed correctly.
Fixed parsing of folded scalar values reported as bug #60, now folded scalars are parsed according to the spec.
Added a new feature allowing to use default parameter values in deserialization to case classes for which YamlCodec or YamlDecoder is derived (#215).

Full Changelog: v0.1.0...v0.2.0