Hi everyone, maybe this is a dumb question but suppose I do this: ```@Serializable data class MyClas...

# serialization

[Chris Fillmore]

Hi everyone, maybe this is a dumb question but suppose I do this:

@Serializable
data class MyClass(val myProp: String, private val myPrivateProp: String)

does myPrivateProp get serialized?

[Marc Knaup]

My guess is that it will, otherwise how would you create a new instance during deserialization if there is no value available for that constructor parameter?

[Chris Fillmore]

good point! thanks @Marc Knaup

[Chris Fillmore]

I suppose I could check easily; sorry I was just reaching out for an easy answer

[Marc Knaup]

btw, data classes don’t really have private properties afaik. You could still access it using .component2(), can’t you? 😄

[Chris Fillmore]

makes sense. I was in a situation last night where I have several similar-but-not-identical requests going out as json, and wanted to share some of the field definitions between them

[Chris Fillmore]

this turned out to be a mess. So instead I just have a bit of duplication across my data classes

[Marc Knaup]

(if you need data at all)

[Chris Fillmore]

Yeah I considered that too

[Chris Fillmore]

I figure it’s probably not a big deal one way or the other. Time will tell if it makes any difference

[Chris Fillmore]

thanks for the feedback

[Nick Johnson]

The serialization plugin will also generate custom code in a companion object to serialize and deserialize, meaning that it can have private access since it is inside the same class

[Chris Fillmore]

ok thanks for the info @Nick Johnson

[Nikky]

imo its not like being able to access stuff via component .. there is loads of other ways to hack visibility modifiers away.. this is all just to make it easier for developers to see that something should not be accessible..