Releases: Kotlin/kotlinx.serialization
1.3.0-RC
This is a release candidate for the next version. It contains a lot of interesting features and improvements,
so we ask you to evaluate it and share your feedback.
Kotlin 1.5.30 is used by default.
Java IO stream-based JSON serialization
Finally, in kotlinx.serialization
1.3.0 we’re presenting the first experimental version of the serialization API for IO streams:
Json.encodeToStream
and Json.decodeFromStream
extension functions.
With this API, you can decode objects directly from files, network connections, and other data sources without reading the data to strings beforehand.
The opposite operation is also available: you can send encoded objects directly to files and other streams in a single API call.
IO stream serialization is available only on the JVM platform and for the JSON format for now.
Check out more in the PR.
Property-level control over defaults values encoding
Previous versions of the library allowed to specify whether to encode or drop default properties values with
format configuration flags such as Json { encodeDefaults = false }
.
In 1.3.0 we’re extending this feature by adding a new way to fine-tune the serialization of default values:
you can now control it on the property level using the new @EncodeDefault
annotation.
@EncodeDefault
annotation has a higher priority over the encodeDefaults
property and takes one of two possible values:
ALWAYS
(default value) encodes a property value even if it equals to default.NEVER
doesn’t encode the default value regardless of the format configuration.
Encoding of the annotated properties is not affected by encodeDefaults
format flag
and works as described for all serialization formats, not only JSON.
To learn more, check corresponding PR.
Excluding null values from JSON serialization
In 1.3.0, we’re introducing one more way to reduce the size of the generated JSON strings: omitting null values.
A new JSON configuration property explicitNulls
defines whether null
property values should be included in the serialized JSON string.
The difference from encodeDefaults
is that explicitNulls = false
flag drops null values even if the property does not have a default value.
Upon deserializing such a missing property, a null
or default value (if it exists) will be used.
To maintain backwards compatibility, this flag is set to true
by default.
You can learn more in the documentation or the PR.
Per-hierarchy polymorphic class discriminators
In previous versions, you could change the discriminator name using the
classDiscriminator property of the Json
instance.
In 1.3.0, we’re adding a way to set a custom discriminator name for each class hierarchy to enable more flexible serialization.
You can do it by annotating a class with @JsonClassDiscriminator
with the discriminator name as its argument.
A custom discriminator is applied to the annotated class and its subclasses.
Only one custom discriminator can be used in each class hierarchy, thanks to the new @InheritableSerialInfo
annotation.
Check out corresponding PR for details.
Support for Java module system
Now all kotlinx.serialization runtime libraries are shipped as a multi-release JAR with module-info.class
file for Java versions 9 and higher.
This enables possibilities to use kotlinx.serialization with modern tools such as jlink
and various technologies such as TorandoFX
.
Many thanks to our contributor Gerard de Leeuw and his PR for making this possible.
Native targets for Apple Silicon
This release includes klibs for new targets, introduced in Kotlin/Native 1.5.30 —
macosArm64
, iosSimulatorArm64
, watchosSimulatorArm64
, and tvosSimulatorArm64
.
Bugfixes and improvements
- Properly handle quoted 'null' literals in lenient mode (#1637)
- Switch on deep recursive function when nested level of JSON is too deep (#1596)
- Support for local serializable classes in IR compiler
- Support default values for
@SerialInfo
annotations in IR compiler - Improve error message for JsonTreeReader (#1597)
- Add guide for delegating serializers and wrapping serial descriptor (#1591)
- Set target JVM version to 8 for Hocon module in Gradle metadata (#1661)
1.2.2
This release contains various bugfixes, some useful features and important performance improvements.
It also uses Kotlin 1.5.20 as default.
Features
- Support for
@JsonNames
andcoerceInputValues
inJson.decodeFromDynamic
(#1479) - Add factory function to wrap a serial descriptor with a custom name for custom delegating serializers (#1547) (thanks to Fadenfire)
- Allow contextually serialized types to be used as map keys in Json (#1552) (thanks to pdvrieze)
Bugfixes and performance improvements
- Update size in
JsonStringBuilder
slow-path to avoid excessive array-copies for large strings with escape symbols (#1491) - Optimize integer encoding length in CBOR (#1570) (thanks to davertay)
- Throw
JsonDecodingException
instead ofClassCastException
during unexpected null inTreeJsonDecoder
(#1550) - Prohibit 'null' strings in lenient mode in order to get rid of 'null' and "null" ambiguity (#1549)
- Avoid usage of reflective-like
serialDescriptor<KType>
in production sources (#1540) - Added correct error message when deserializing missing enum member for Properties format (#1539)
- Make
DescriptorSchemaCache
in Json thread-local on Native (#1484)
1.2.1
This release mainly contains bugfixes for various issues, including important broken thread-safety and improper encoding.
Features
- Added support for nullable values, nested and empty collections in protobuf (#1430)
Bugfixes
- Support @JsonNames for enum values (#1473)
- Handle EOF in skipElement correctly (#1475)
- Allow using value classes with primitive carriers as map keys (#1470)
- Read JsonNull only for non-string literals in JsonTreeReader (#1466)
- Properly reuse JsonStringBuilders in CharArrayPool (#1455)
- Properly ensure capacity of the string builder on the append slow-path (#1441)
1.2.0
This release has some known critical bugs, so we advise to use 1.2.1 instead.
This release contains a lot of new features and important improvements listed below;
Kotlin 1.5.0 is used as a default compiler and language version.
JSON performance improvements
JSON encoder and decoder were revisited and significantly rewritten,
which lead us to up to 2-3x times speedup in certain cases.
Additional details can be found in the corresponding pull requests: [1], [2].
Ability to specify alternative names during JSON decoding
The one of the most voted issues is fixed now — it is possible to specify multiple names for one property
using new @JsonNames
annotation.
Unlike @SerialName
, it only affects JSON decoding, so it is useful when dealing with different versions of the API.
We've prepared a documentation for you about it.
JsonConfiguration in public API
JsonConfiguration
is exposed as a property of Json
instance. You can use it to adjust behavior in
your custom serializers.
Check out more in the corresponding issue and the PR.
Generator for .proto files based on serializable Kotlin classes
Our implementation of Protocol Buffers format uses @Serializable
Kotlin classes as a source of schema.
This is very convenient for Kotlin-to-Kotlin communication, but makes interoperability between languages complicated.
To resolve this issue, we now have a
schema generator that can produce .proto files out of Kotlin classes. Using it, you can keep Kotlin
classes as a source of truth and use traditional protoc compilers for other languages at the same time.
To learn more, check out the documentation for the new ProtoBufSchemaGenerator
class or
visit the corresponding PR.
Note: this generator is on its experimental stage and any feedback is very welcomed.
Contextual serialization of generic classes
Before 1.2.0, it was impossible to register context serializer for generic class,
because contextual
function accepted a single serializer.
Now it is possible to register a provider — lambda that allows to construct a serializer for generic class
out of its type arguments serializers. See the details in the documentation.
Other features
- Support for watchosX64 target (#1366).
- Introduce kotlinx-serialization-bom (#1356).
- Support serializer on JS IR when T is an interface (#1431).
Bugfixes
1.1.0
This release contains all features and bugfixes from 1.1.0-RC plus an additional fix for incorrect exception type
(#1325 — Throw SerializationException
instead of IllegalStateException
in EnumSerializer
) and uses release version of Kotlin 1.4.30.
In the light of JCenter shutdown, starting from 1.1.0-RC and now on,
all new releases of kotlinx.serialization are published directly to Maven Central and therefore are not available in https://kotlin.bintray.com/kotlinx/
repository.
We suggest you to remove jcenter()
and other kotlin bintray repositories from your buildscripts and to use mavenCentral()
repository instead.
1.1.0-RC
This is a release candidate of 1.1.0 version. Note that final 1.1.0 version may include more features and bugfixes,
which would be listed in the corresponding changelog.
Kotlin version requirement updated
Due to changes in calling conventions between compiler plugin and serialization core runtime, this release requires
Kotlin version at least 1.4.30-M1 (we recommend using 1.4.30 release version). However, these changes should not affect your code, because only deprecated functions were removed from public API.
See corresponding PR for the details.
Experimental support for inline classes (IR only)
Using 1.1.0-RC, you can mark inline classes as @Serializable
and use them in other serializable classes.
Unsigned integer types (UByte
, UShort
, UInt
and ULong
) are serializable as well and have special support in JSON.
This feature requires Kotlin compiler 1.4.30-RC and enabling new IR compilers for JS and JVM.
You can learn more in the documentation and corresponding pull request.
Other features
- Add
serializerOrNull
function forKType
andType
arguments (#1164) - Allow shared prefix names in
Properties
(#1183) (thanks to TorRanfelt) - Add support for encoding/decoding
Properties
values as Strings (#1158) (thanks to daniel-jasinski)
Bugfixes and performance improvements
- Support contextual serialization for derived classes (#1277) (thanks to Martin Raison)
- Ensure serialization is usable from K/N background thread (#1282)
- Fail on primitive type overflow during
JsonElement
deserialization (#1300) - Throw
SerializationException
instead of ISE when encountering an invalid boolean in JSON (#1299) - Optimize the loop for writing large varints in
ProtoBuf
(#1294) - Fix serializing property with custom accessors and backing field (#1197)
- Optimize check for missing fields in deserialization and improve
MissingFieldException
message (#1153) - Improved support of nullable serializer in
@UseSerializers
annotation (#1195) - Correctly escape keys in
JsonObject.toString()
(#1246) (thanks to Karlatemp) - Treat
Collection
asArrayList
in serializer by type lookups (#1257) - Do not try to end structure in encode/decode structure extensions if an exception has been thrown, so the original exception will be propagated (#1201)
- Properly cache serial names in order to improve performance of JSON parser with strict mode (#1209)
- Fix dynamic serialization for nullable values (#1199) (thanks to ankushg)
1.0.1
This patch release contains several feature improvements as well as bugfixes and performance improvements.
Features
- Add object-based serialization and deserialization of polymorphic types for
dynamic
conversions on JS platform (#1122) - Add support for object polymorphism in HOCON decoder (#1136)
- Add support of decoding map in the root of HOCON config (#1106)
Bugfixes
- Properly cache generated serializers in PluginGeneratedSerialDescriptor (#1159)
- Add Pair and Triple to serializer resolving from Java type token (#1160)
- Fix deserialization of half-precision, float and double types in CBOR (#1112)
- Fix ByteString annotation detection when ByteArray is nullable (#1139) (thanks to Travis Wyatt)
1.0.0
The first public stable release, yay!
The definitions of stability and backwards compatibility guarantees are located in the corresponding document.
We now also have a GitHub Pages site with full API reference.
Compared to RC2, no new features apart from #947 were added and all previously deprecated declarations and migrations were deleted.
If you are using RC/RC2 along with deprecated declarations, please, migrate before updating to 1.0.0.
In case you are using pre-1.0 versions (e.g. 0.20.0), please refer to our migration guide.
Bugfixes and improvements
- Support nullable types at top-level for JsonElement decoding (#1117)
- Add CBOR ignoreUnknownKeys option (#947) (thanks to Travis Wyatt)
- Fix incorrect documentation of
encodeDefaults
(#1108) (thanks to Anders Carling)
1.0.0-RC2
Second release candidate for 1.0.0 version. This RC contains tweaks and changes based on users feedback after 1.0.0-RC.
Major changes
JSON format is now located in different artifact (#994)
In 1.0.0-RC, the kotlinx-serialization-core
artifact contained core serialization entities as well as Json
serial format.
We've decided to change that and to make core
format-agnostic.
It would make the life easier for those who use other serial formats and also make possible to write your own implementation of JSON
or another format without unnecessary dependency on the default one.
In 1.0.0-RC2, Json
class and related entities are located in kotlinx-serialization-json
artifact.
To migrate, simply replace kotlinx-serialization-core
dependency with -json
. Core library then will be included automatically
as the transitive dependency.
For most use-cases, you should use new kotlinx-serialization-json
artifact. Use kotlinx-serialization-core
if you are
writing a library that depends on kotlinx.serialization in a format-agnostic way of provides its own serial format.
encodeDefaults
flag is now set to false
in the default configuration for JSON, CBOR and Protocol Buffers.
The change is motivated by the fact that in most real-life scenarios, this flag is set to false
anyway,
because such configuration reduces visual clutter and saves amount of data being serialized.
Other libraries, like GSON and Moshi, also have this behavior by default.
This may change how your serialized data looks like, if you have not set value for encodeDefaults
flag explicitly.
We anticipate that most users already had done this, so no migration is required.
In case you need to return to the old behavior, simply add encodeDefaults = true
to your configuration while creating Json/Cbor/ProtoBuf
object.
Move Json.encodeToDynamic/Json.decodeFromDynamic
functions to json package
Since these functions are no longer exposed via DynamicObjectParser/Serializer
and they are now Json
class extensions,
they should be moved to kotlinx.serialization.json
package.
To migrate, simply add import kotlinx.serialization.json.*
to your files.
Bugfixes and improvements
- Do not provide default implementation for serializersModule in AbstractEncoder/Decoder (#1089)
- Support JsonElement hierarchy in
dynamic
encoding/decoding (#1080) - Support top-level primitives and primitive map keys in
dynamic
encoding/decoding - Change core annotations retention (#1083)
- Fix 'Duplicate class ... found in modules' on Gradle != 6.1.1 (#996)
- Various documentation clarifications
- Support deserialization of top-level nullable types (#1038)
- Make most serialization exceptions eligible for coroutines exception recovery (#1054)
- Get rid of methods that do not present in Android API<24 (#1013, #1040)
- Throw JsonDecodingException on empty string literal at the end of the input (#1011)
- Remove new lines in deprecation warnings that caused errors in ObjC interop (#990)
1.0.0-RC
Release candidate for 1.0.0 version. The goal of RC release is to collect feedback from users
and provide 1.0.0 release with bug fixes and improvements based on that feedback.
While working on 1.0.0 version, we carefully examined every public API declaration of the library and
split it to stable API, that we promise to be source and binary-compatible,
and experimental API, that may be changed in the future.
Experimental API is annotated with @ExperimentalSerializationApi
annotation, which requires opt-in.
For a more detailed description of the guarantees, please refer to the compatibility guide.
The id of the core artifact with @Serializable
annotation and Json
format was changed
from kotlinx-serialization-runtime
to kotlinx-serialization-core
to be more clear and aligned with other kotlinx libraries.
A significant part of the public API was renamed or extracted to a separate package.
To migrate from the previous versions of the library, please refer to the migration guide.
API changes
Json
-
Core API changes
stringify
andparse
are renamed toencodeToString
anddecodeFromString
parseJson
andfromJson
are renamed toparseToJsonElement
anddecodeFromJsonElement
- Reified versions of methods are extracted to extensions
-
Json
constructor is replaced withJson {}
builder function,JsonConfiguration
is deprecated in favor
ofJson {}
builder- All default
Json
implementations are removed Json
companion object extendsJson
- All default
-
Json configuration
prettyPrintIndent
allows only whitespacesserializeSpecialFloatingPointValues
is renamed toallowSpecialFloatingPointValues
. It now affects both serialization and deserialization behaviourunquoted
JSON flag is deprecated for removal- New
coerceInputValues
option for null-defaults and unknown enums (#90, #246)
-
Simplification of
JsonElement
API- Redundant members of
JsonElement
API are deprecated or extracted to extensions - Potential error-prone API is removed
JsonLiteral
is deprecated in favor ofJsonPrimitive
constructors with nullable parameter
- Redundant members of
-
JsonElement
builders rework to be aligned with stdlib collection builders (#418, #627)- Deprecated infix
to
and unaryPlus in JSON DSL in favor ofput
/add
functions jsonObject {}
andjson {}
builders are renamed tobuildJsonObject {}
andbuildJsonArray {}
- Make all builders
inline
(#703)
- Deprecated infix
-
JavaScript support
DynamicObjectParser
is deprecated in the favor ofJson.decodeFromDynamic
extension functionsJson.encodeToDynamic
extension is added as a counterpart toJson.decodeFromDynamic
(formerDynamicObjectParser
) (#116)
-
Other API changes:
JsonInput
andJsonOutput
are renamed toJsonDecoder
andJsonEncoder
- Methods in
JsonTransformingSerializer
are renamed totransformSerialize
andtransformDeserialize
JsonParametricSerializer
is renamed toJsonContentPolymorphicSerializer
JsonEncodingException
andJsonDecodingException
are made internal
-
Bug fixes
Core API for format authoring
-
The new naming scheme for
SerialFormats
- Core functions in
StringFormat
andBinaryFormat
are renamed and now follow the same naming scheme stringify
/parse
are renamed toencodeToString
/decodeFromString
encodeToByteArray
/encodeToHexString
/decodeFromByteArray
/decodeFromHexString
inBinaryFormat
are introduced instead ofdump
/dumps
/load
/loads
- Core functions in
-
New format instances building convention
- Constructors replaced with builder-function with the same name to have the ability to add new configuration parameters,
while preserving both source and binary compatibility - Format's companion objects now extend format class and can be used interchangeably
- Constructors replaced with builder-function with the same name to have the ability to add new configuration parameters,
-
SerialDescriptor-related API
SerialDescriptor
andSerialKind
are moved to a separatekotlinx.serialization.descriptors
packageENUM
andCONTEXTUAL
kinds now extendSerialKind
directlyPrimitiveDescriptor
is renamed toPrimitiveSerialDescriptor
- Provide specific
buildClassSerialDescriptor
to use with classes' custom serializers, creating other kinds is considered experimental for now - Replace extensions that returned lists (e.g.
elementDescriptors
) with properties that return iterable as an optimization IndexOutOfBoundsException
indescriptor.getElementDescriptor(index)
forList
after upgrade to 0.20.0 is fixed (#739)
-
SerializersModule-related API
SerialModule
is renamed toSerializersModule
SerialModuleCollector
is renamed toSerializersModuleCollector
- All builders renamed to be aligned with a single naming scheme (e.g.
SerializersModule {}
DSL) - Deprecate infix
with
in polymorphic builder in favor of subclass() - Helper-like API is extracted to extension functions where possible.
polymorphicDefault
API for cases when type discriminator is not registered or absent (#902)
-
Contextual serialization
-
Encoding-related API
- Encoding-related classes (
Encoder
,Decoder
,AbstractEncoder
,AbstractDecoder
) are moved to a separatekotlinx.serialization.encoding
package - Deprecated
typeParameters
argument inbeginStructure
/beginCollectio
n methods - Deprecated
updateSerializableValue
and similar methods andUpdateMode
enum - Renamed
READ_DONE
toDECODE_DONE
- Make extensions
inline
where applicable kotlinx.io
mockery (InputStream
,ByteArrayInput
, etc) is removed
- Encoding-related classes (
-
Serializer-related API
UnitSerializer
is replaced withUnit.serializer()
- All methods for serializers retrieval are renamed to
serializer
- Context is used as a fallback in
serializer
by KType/Java's Reflect Type functions (#902, #903) - Deprecated all exceptions except
SerializationException
. @ImplicitReflectionSerializer
is deprecated- Support of custom serializers for nullable types is added (#824)
ProtoBuf
ProtoBuf
constructor is replaced withProtoBuf {}
builder functionProtoBuf
companion object now extendsProtoBuf
ProtoId
is renamed toProtoNumber
,ProtoNumberType
toProtoIntegerType
to be consistent with ProtoBuf specification- ProtoBuf performance is significantly (from 2 to 10 times) improved (#216)
- Top-level primitives, classes and objects are supported in ProtoBuf as length-prefixed tagless messages (#93)
SerializationException
is thrown instead ofIllegalStateException
on incorrect input (#870)ProtobufDecodingException
is made internal
Other formats
- All format constructors are migrated to builder scheme
- Properties serialize and deserialize enums as strings (#818)
- CBOR major type 2 (byte string) support (#842)
ConfigParser
is renamed toHocon
,kotlinx-serialization-runtime-configparser
artifact is renamed tokotlinx-serialization-hocon
- Do not write/read size of collection into Properties' map (#743)