I found out recently that there is an XML implementation for kotlinx.serialization: https://github.com/pdvrieze/xmlutil
It's not first party, unlike JSON, but if we add kotlinx.serialization already for #70 it makes a lot of sense to switch.
xmlutil currently supports Android, JVM and JS; it would be good to switch to that, if it works for us. Getting Android support sounds very useful. This issue is a placeholder to experiment with kotlinx.serialization and seeing how it works. Switching to a Multiplatform project means we'll need to change our publication strategy (have a core, and separate jvm and android artifacts that depend on that, as a minimum) so it's reserved for a major version — could be a v2.0 headline feature.
The actual conversion to MP is taken care of as part of #63 — the goal of this issue is merely to switch our current jvm-only implementation. It could even be shipped in a 1.x release since it's not exposed to users.
I found out recently that there is an XML implementation for kotlinx.serialization: https://github.com/pdvrieze/xmlutil
It's not first party, unlike JSON, but if we add kotlinx.serialization already for #70 it makes a lot of sense to switch.
xmlutilcurrently supports Android, JVM and JS; it would be good to switch to that, if it works for us. Getting Android support sounds very useful. This issue is a placeholder to experiment with kotlinx.serialization and seeing how it works. Switching to a Multiplatform project means we'll need to change our publication strategy (have acore, and separatejvmandandroidartifacts that depend on that, as a minimum) so it's reserved for a major version — could be a v2.0 headline feature.The actual conversion to MP is taken care of as part of #63 — the goal of this issue is merely to switch our current jvm-only implementation. It could even be shipped in a 1.x release since it's not exposed to users.