wei
10/05/2018, 2:43 AMdeleted
and that exception was gone. So it has to be because of the unconventional behavior causing the exception.Mike
10/05/2018, 10:26 AMis
instead of get
for boolean fields, so the mapper should detect that correctly.
I notice that IntelliJ generates isDeleted
method by default for a Java boolean field whether the field is called deleted
or isDeleted
.
I would guess the mapper is the problem and is very literally looking for either getIsDeleted
or isIsDeleted
methods, and not finding them.
Time to talk to mapper writers?Dico
10/05/2018, 11:21 AM@get:JvmName("getIsDeleted")
@set:JvmName("setIsDeleted")
var isDeleted: Boolean