Support for serialization
See original GitHub issueIt would be nice to have support for kotlinx.serialization so we dont have to implement a serializer by hand when Uuid
is used in a @Serializable
class.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:6 (3 by maintainers)
Top Results From Across the Web
What is serialization and how does it work? - Hazelcast
Serialization encompasses both the storage of the object and exchange of data. Since objects are composed of several components, saving or delivering all...
Read more >Serialization guidelines | Microsoft Learn
Types can support data contract serialization by applying the DataContractAttribute to the type and the DataMemberAttribute to the members ( ...
Read more >Serialization - Wikipedia
Go also supports Gobs. In Haskell, serialization is supported for types that are members of the Read and Show type classes. Every type...
Read more >Object Serialization: Frequently Asked Questions - Oracle
Are there any plans to support the serialization of threaded objects? In JDK 1.1, Threads will not be serializable. In the present implementation, ......
Read more >Different Serialization Approaches for Java - Baeldung
It's a simple yet extensible mechanism · It maintains the object type and safety properties in the serialized form · Extensible to support ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’d also want to have it be serialized differently depending on the input/ouput format. I think implementing this right now in kotlinx.serialization is kind of kludgy. I think improvements to this are coming with their next release though.
Even though kotlinx.serialization went 1.0.0 today.
@Serializer(forClass…
is still considered experimental API. For that reason, I think breaking it out into its own module makes sense. Offhand, I’m not sure what would happen if one were to upgrade uuid and kotlinx.serialization at the same time in your project, but then the API we were using for serialization became incompatible. With a separate module, it might be less of an issue for most users.