Bump kotlinx-serialization-json from 1.1.0 to 1.2.0

[dependabot]

Bumps kotlinx-serialization-json from 1.1.0 to 1.2.0.

Release notes

Sourced from kotlinx-serialization-json's releases.

1.2.0

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

... (truncated)

Changelog

Sourced from kotlinx-serialization-json's changelog.

1.2.0 / 2021-04-27

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 issues: [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).

... (truncated)

Commits

• fc9343f Update Kotlin and add changelog for 1.2.0 (#1436)
• 75566cc Generator for .proto files based on serializable Kotlin classes (#1255)
• 38adb1b Support serializer<T> on JS IR when T is an interface (#1431)
• f8f37a3 Merge remote-tracking branch 'origin/master' into dev
• c6025c9 Support contextual serialization of generic classes (#1416)
• 59d3216 Make JsonConfiguration public and expose it for custom serializers (#1409)
• 436cf83 Replace Array<String> in JsonNames with vararg
• f7b7f19 Fix incorrect skipElement() when string literals contain ] or }
• 6087755 Add @​JsonNames annotation
• 83d0faa Fix serializer lookup by KType for third party generics (#1397)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)