Open majkrzak opened 5 years ago
This is a conceptual limitation. See, on deserialization, when the lol
field is missing, you need to recreate it as bar.toLowerCase()
(properties with default values are considered optional). But you can't because you don't have bar
. It's not even a field, so it has no chance to be serialized. Therefore such classes can't be serializable.
You are messing serialization and deserialization. Also class can be deserialized if delegate provides the setvalue
Yes, I'm talking about deserialization. While 'serializable-only' concept is legit and has its use cases, this library focuses on making both processes available without corner cases, so making a class serializable and non-deserialziable at the same time is a non-goal.
Also class can be deserialized if delegate provides the setvalue
That's what I've mentioned in the issue about delegates.
Sorry, I've messed the tickets.
Describe the bug When class constructors contains non property parameter it can not be made serializable with @Serializable annotaion
To Reproduce
Expected behavior
Environment