Bump org.jetbrains.kotlinx:kotlinx-serialization-json from 1.6.3 to 1.7.0
Bumps org.jetbrains.kotlinx:kotlinx-serialization-json from 1.6.3 to 1.7.0.
Release notes
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.
1.7.0
This release contains all of the changes from 1.7.0-RC and is compatible with Kotlin 2.0. Please note that for reasons explained in the 1.7.0-RC changelog, it may not be possible to use it with the Kotlin 1.9.x compiler plugin. Yet, it is still fully backward compatible with previous versions.
The only difference with 1.7.0-RC is that the
classDiscriminatorMode
property inJsonBuilder
is marked as experimental, as it should have been when it was introduced (#2680).1.7.0-RC
This is a release candidate for the next version. It is based on Kotlin 2.0.0-RC3 and is fully compatible with a stable Kotlin 2.0 release. Due to a potential breaking change (see below), it requires a compiler plugin with a version at least of 2.0.0-RC1.
Important change: priority of PolymorphicSerializer for interfaces during call to serializer() function
Non-sealed interfaces in kotlinx.serialization are always serializable with a polymorphic serializer, even if they do not have
@Serializable
annotation. This also means thatserializersModule.serializer<SomeInterface>()
call will return you a serializer capable of polymorphism. This function was written in a way that it unconditionally returns aPolymorphicSerializer
if type argument is a non-sealed interface. This caused problems withSerializersModule
functionality, because actual module was not taken into consideration, and therefore it was impossible to override serializer for interface using 'contextual serialization' feature. The problem is described in detail here. To overcome these problems, we had to change the behavior of this function regarding interfaces. It now looks intoSerializersModule
first ifT
is a non-sealed interface, and only if there is no registered contextual serializer forT
, it returns a polymorphic serializer.Behavior before 1.7.0-RC:
interface SomeInterface val module = SerializersModule { contextual(SomeInterface::class, CustomSomeInterfaceSerializer) } // Prints PolymorphicSerializer<SomeInterface>: println(module.serializer<SomeInterface>())
Behavior in 1.7.0-RC, 1.7.0, and higher:
interface SomeInterface val module = SerializersModule { contextual(SomeInterface::class, CustomSomeInterfaceSerializer) } // Prints CustomSomeInterfaceSerializer: println(module.serializer<SomeInterface>())
We expect minimal impact from this change, but be aware of it anyway. Implementation details are available in this PR.
Due to the serializer() function being also a compiler intrinsic, code of kotlinx.serialization compiler plugin also accommodates this change in the 2.0 branch. To get a consistent result from both plugin and runtime, kotlinx.serialization compiler plugin should be at least of 2.0.0-RC1 version. To verify so, 1.7.0-RC runtime will be rejected by older plugins.
... (truncated)
Changelog
Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.
1.7.0 / 2024-06-05
This release contains all of the changes from 1.7.0-RC and is compatible with Kotlin 2.0. Please note that for reasons explained in the 1.7.0-RC changelog, it may not be possible to use it with the Kotlin 1.9.x compiler plugin. Yet, it is still fully backwards compatible with previous versions.
The only difference with 1.7.0-RC is that
classDiscriminatorMode
property inJsonBuilder
is marked as experimental, as it should have been when it was introduced (#2680).1.7.0-RC / 2024-05-16
This is a release candidate for the next version. It is based on Kotlin 2.0.0-RC3 and is fully compatible with a stable Kotlin 2.0 release. Due to a potential breaking change (see below), it requires a compiler plugin with a version at least of 2.0.0-RC1.
Important change: priority of PolymorphicSerializer for interfaces during call to serializer() function
Non-sealed interfaces in kotlinx.serialization are always serializable with a polymorphic serializer, even if they do not have
@Serializable
annotation. This also means thatserializersModule.serializer<SomeInterface>()
call will return you a serializer capable of polymorphism. This function was written in a way that it unconditionally returns aPolymorphicSerializer
if type argument is a non-sealed interface. This caused problems withSerializersModule
functionality, because actual module was not taken into consideration, and therefore it was impossible to override serializer for interface using 'contextual serialization' feature. The problem is described in details here. To overcome these problems, we had to change the behavior of this function regarding interfaces. It now looks intoSerializersModule
first ifT
is a non-sealed interface, and only if there is no registered contextual serializer forT
, it returns a polymorphic serializer.Behavior before 1.7.0-RC:
interface SomeInterface val module = SerializersModule { contextual(SomeInterface::class, CustomSomeInterfaceSerializer) } // Prints PolymorphicSerializer<SomeInterface>: println(module.serializer<SomeInterface>())
Behavior in 1.7.0-RC, 1.7.0, and higher:
interface SomeInterface val module = SerializersModule { contextual(SomeInterface::class, CustomSomeInterfaceSerializer) } // Prints CustomSomeInterfaceSerializer: println(module.serializer<SomeInterface>()) </tr></table>
... (truncated)
Commits
-
d2dc7d2
Update to Kotlin 2.0 and prepare 1.7.0 release (#2706) -
1cac162
Merge remote-tracking branch 'origin/master' into dev -
fbd0734
Use@PublishedApi
annotation on functions called from plugin-generated code (... -
4bf4113
Add bencoding to community-supported formats (#2687) -
c487e78
JSON: Fix mutableclassDiscriminatorMode
in config, and mark experimental i... -
385c97d
Remove yellow code (#2691) -
688f64b
Added link to kotlinx-serialization-smile in the formats list (#2689) -
1f38e22
Add additional repository -
dd1b76e
Prepare Changelog and Readme for 1.7.0-RC release -
b4bf182
Raise Require-Kotlin-Version to 2.0.0-RC1 - Additional commits viewable in compare view
Dependabot commands
You can trigger Dependabot actions by commenting on this MR
-
$dependabot recreate
will recreate this MR rewriting all the manual changes and resolving conflicts