Skip to content

Releases: pdvrieze/xmlutil

The modular update

30 Jun 03:56
Compare
Choose a tag to compare
  • This version has been refactored to allow for a modular version. A separate modular branch exists as well, but some testing of it would be beneficial.
  • Make it work properly again with the new serialization generation in 1.3.30 (this version targets 1.3.40)
  • Refactored packages. Mostly the packages that contain utility classes that were intended mainly for internal use.
  • Update to work against kotlinx.serialization 0.11.0/0.11.1
  • Change versioning system. Instead of independent versions, use a version that reflects the underlying kotlinx.serialization version. At least as long as kotlinx.serialization is still unstable.
  • Split out a serialutil package that contains helpers for implementing serializers in classes.

JavaScript here we come

03 Apr 20:50
Compare
Choose a tag to compare

This version adds support for Javascript serialization and deserialization. It fixes the Javascript core library as well.
Further it contains various bug fixes in the existing java-ish platform support.

Follow on to 0.10.0 of the serialization framework

08 Feb 22:15
Compare
Choose a tag to compare
  • Update to kotlinx.serialization 0.10.0
  • Remove the Canary code as elementDescriptors are now generated
  • Some caching and stability is still provided
  • NOTE: Custom serializers do need to provide elementDescriptors

Kotlin 1.3.0 update

03 Nov 17:13
Compare
Choose a tag to compare

Update the package to work with Kotlin 1.3.0 and serialization library 0.9.0. This means that some of the API has changed a bit (parameter order) and reflection based access is marked experimental in line with the serialization library itself as that doesn't work on non-java platforms.

Rework for stability

03 Oct 07:58
Compare
Choose a tag to compare

This release updates the serialization plugin to be based upon the design described in the serialization keep. This has improved architecture and dependability.

  • Naming is now well defined: If present on type or use site the XmlName tag wins. Otherwise for tags the serialization name at the type declaration wins (XML tags should be named the same independent of use). For attributes the use site name wins (attributes are generally primitives and generic type names are not useful)

Initial release

03 Oct 07:58
Compare
Choose a tag to compare

The initial release of the project