v1.1.0
What's New
- Adds support for different paths to the version field. You achieve this by creating a
Codable
type that adoptsVersionPathSpec
, and specifying this on yourVersionedCodable
type.- The default behaviour is unchanged and is available as
VersionKeyAtRootVersionPathSpec
. This is automatically chosen for you if you do not specify aVersionSpec
in yourVersionedCodable
.
- The default behaviour is unchanged and is available as
- Removes support for throwing
VersionedEncodingError.typeHasClashingVersionField
encode time if the type has aversion
key. This was an expensive operation which wouldn't work anyway with different key paths to the version field. In an ideal world it would be possible to test this at compile time, but I don't currently see how this is possible without a compiler plugin. - Improves documentation. Documentation is now deployed with links to the source code.
Full Changelog: 1.0.2...v1.1.0