Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Auto generated GetResolver has constructor with wrong parameter order in Kotlin

See original GitHub issue

Reproduction steps:

create class with more than two columns f.e.

@StorIOSQLiteType(table = "CreditCard")
data class CreditCard @StorIOSQLiteCreator constructor(
        @get:StorIOSQLiteColumn(name = "id", key = true) val cardId: Long,
        @get:StorIOSQLiteColumn(name = "name") val name: String,
        @get:StorIOSQLiteColumn(name = "expireYear") val expireYear: Int,
        @get:StorIOSQLiteColumn(name = "expireMonth") val expireMonth: Int,
        @get:StorIOSQLiteColumn(name = "type") val type: String,
        @get:StorIOSQLiteColumn(name = "isDefault") val isDefault: Boolean)

build project (couple of times if needed).

The reason for that is kapt (kotlins annotation processor, don’t know about apt) does not process annotations in creation order.

Issue Analytics

State:
Created 7 years ago
Comments:18 (3 by maintainers)

Top GitHub Comments

2reactions

geralt-encorecommented, Dec 17, 2016

I just checked that @pbochenski is actually right and you can get actual parameters names from getParameters() on ExecutableElement. So it should be possible to map columns with parameters relying just on their names.

0reactions

geralt-encorecommented, Jan 3, 2017

That’s a bummer 😔 I tested it properly before making PR with the fix and it worked. Need to investigate it further…