<https://twitter.com/sdeleuze/status/1095714310712...

# spring

[sdeleuze]

https://twitter.com/sdeleuze/status/1095714310712709120

[masc3d]

won’t explicit override do?

override fun getId(): Long? = this.id

[masc3d]

referring to https://gist.github.com/sdeleuze/1820ee016d8c2e480d9b

[sdeleuze]

With non data classes it works yes, even if ugly

[sdeleuze]

class User(
		id: Long?,
		val firstName: String,
		val lastName: String) : Persistable<Long?> {

	override fun isNew() = (id == null)

	override fun getId(): Long? = this.id
}

[sdeleuze]

With data classes there is a declaration clash

[sdeleuze]

Or it can work if you use another name for id, so still pretty ugly

[sdeleuze]

Oh and your proposal won't work because the is confusion between the property and the getter, so infinite recursion

[sdeleuze]

More details about the possible alternative in https://youtrack.jetbrains.com/issue/KT-6653#focus=streamItem-27-3290694-0-0

[masc3d]

im sure there’s another ugly way around recursion. but why not have dedicated support for kt properties in spring then? pretty sure, kt-6653 won’t be resolved

[thanksforallthefish]

this is not just a spring issue, maybe worth sharing in #general. it is really a kotlin/java limitation

[masc3d]

yes it’s true, but not that serious imho. you can still do anything you want to do, just less pretty for very specific cases.

[masc3d]

just wanted to point out there’s at least one or two alternative solutions for spring-data which can be pretty without waiting that kt-6653 happens some day.