Is it necessary that properties without backing fi...
# serializationg
grandstaish
09/10/2018, 10:08 AMIs it necessary that properties without backing fields are serialized?
k
karelpeeters
09/10/2018, 10:32 AMBarring global variables they should be derivable from the actual state of the class, so no?
g
grandstaish
09/10/2018, 10:50 AMyeah — that's my assumption too. But looking at the compiled code for my classes, kotlinx.Serialization seems to serialize them.
Actually I think this is probably a bug. It even generates a new constructor, where the constructor tries to set fields that don't exist
s
sandwwraith
09/10/2018, 11:02 AMI think there should be an assertion in plugin somewhere, which forces user to mark such properties as
@Transientg
grandstaish
09/10/2018, 11:11 AMCouldn't they be excluded automatically?
s
sandwwraith
09/10/2018, 11:13 AMWe don’t have an opt-in annotation (inverse to transient), so if there is a need to serialize computed property (e. g. for external client or for logging), auto-exclusion would made this case impossible
13 Views