0.5.12
BREAKING CHANGES
This release resolves a cross-platform representation mismatch of Dates (the Automerge .timestamp scalar value), documented at #139. When I implemented the swift overlay, I missed that the Int64 value stored was in milliseconds, instead of seconds, so the date conversions for cross-platform were being incorrectly interpreted.
The effect of this is that dates from other platforms were interpretted incorrectly. Now with the fix, dates you have in existing Automerge documents that were created with earlier versions of this swift framework will be incorrect, as they were stored with the expectations of seconds since epoch rather than milliseonds since epoch. If you're using any timestamps/dates in your models, the workaround to fix previously encoded data is to read the raw scalar value from the document and multiply or divide the value (depending on which way you're going) by 1000 to get to a corrected value.
What's Changed
- updating UniFFI to version 0.27.0 by @heckj in #135
- Adds support to encode & decode Foundation.URL by @lightsprint09 in #136
- Removes force downcast in favor of condidional cast in switch by @lightsprint09 in #137
- Improve Semantic of ScalarValueRepresentable by @lightsprint09 in #140
- Use millisecond semantic to match automerge-core by @lightsprint09 in #141
- Support for URLs in lists by @lightsprint09 in #142
- Interop tests by @heckj in #143
New Contributors
- @lightsprint09 made their first contribution in #136
Full Changelog: 0.5.11...0.5.12
