https://kotlinlang.org logo
Join Slack
Powered by
:mega: kotlinx.serialization `0.14.0` has been rel...
# serialization
s
📣 kotlinx.serialization 
0.14.0
has been released! This release contains some breaking changes and requires Kotlin 1.3.60 to work on all platforms. Some highlights: • Support for tvOS and watchOS in all flavours (added in Kotlin/Native 1.3.60) • Special support for serializing Kotlin's `object`s and 
sealed class
es. See updated docs: https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/polymorphism.md#sealed-classes. • Enums now should support 
@SerialName
and other specific annotations (but they should be marked 
@Serializable
). Full changelog: https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md#v0140--2019-11-19
🎉 21
f
Heh, this update gave a lot of compile errors for my serialization format
EnumDescriptor
is now 
SerialDescriptor
in 
encodeEnum
s
Yes, this should be the only change in interfaces
f
There is also the UnionKind.POLYMORPHIC change 🙂
a
Are there any chances to fix https://github.com/Kotlin/kotlinx.serialization/issues/378 anytime soon?
t
@sandwwraith Inline class serialization is out of 
1.3
? OOB serialization - 
1.4
?
s
Inline classes are next in the roadmap after sealed classes.
👍 1
@altavir To be honest, this problem can be solved by sorting class' properties by name in SerialDescriptor. However, this will lead to JSON outputs where all properties are sorted in alphabetical order, not in source-code order. Although we didn't give any particular guarantees about that order, this will be a big semantic change which some people don't want
a
I commented it in the issue. One can add additional orderering property to the descriptor. Currently the issue blocks significant part of library usability, since we can't inherit seialzeable classes from other modules
The only workaround is to move everything in the module, where it is used.
t
Do you use DCE?
a
No, I am talking about JVM mostly
2 Views
Open in Slack
PreviousNext
Powered by