A modern programming language that makes developers happier.

kotlinlang

^^ I changed the name of the data class field to `deleted` and that exception was gone. So it has to be because of the unconventional behavior causing the exception.

It’s definitely the name. It’s somewhat Java convention to use `is` 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?

```
@get:JvmName("getIsDeleted")
@set:JvmName("setIsDeleted")
var isDeleted: Boolean
```