What’s the right way to do a Data Class such that ...

# announcements

[Michael]

What’s the right way to do a Data Class such that it can “implement an interface that requires one getter”? The data class is just doing what it’s doing, I just need to pass it to a method that requires one getter (which it would have)

[Shawn]

java interface?

[Michael]

yeah.

[Shawn]

if you need to reuse this class, you can always just make the field a private/internal val and implement an override fun getFoo()

[Michael]

It’s just a pojo - a bag of DB columns.

[Shawn]

I’m not sure what you’re implying by that

[Shawn]

the getter you implement is just a utility getter to satisfy the interface’s requirements

[Shawn]

unfortunately we can’t use kotlin property getters and setters to do so - we just run into JVM platform declaration clashes

[Michael]

Just trying to make sure I’m understand the limitations and solutions. I just need to make that particular property private and expose getter/setter methods, like I would do in Java?

[Shawn]

More or less, yes. If it’s a val you of course don’t have to write a setter

[Shawn]

also if you make it an internal val, you can avoid having to use the getter within Kotlin

[Shawn]

so in your Kotlin code you can still just call pojo.field

[Shawn]

this is specifically for Java interfaces. unfortunately JB hasn’t really given us an elegant solution to this issue

[Shawn]

it might honestly be by design, in order to differentiate between interface methods and properties in general

[Michael]

It’s a frustrating ambiguity in the java world.

[Michael]

Hmm. If I make the interface kotlin, and shift the work to the java side, that actually seems smoother.

[Michael]

Since in a kotlin interface, I can have a property.

[Michael]

Thanks for going through that with me. 🙂

[Shawn]

no problem! everyone needs a rubber duck from time to time lol