IssueTracker

Some related issues I found regrading this area:

• https://stackoverflow.com/questions/35976002/how-to-use-android-support-typedef-annotations-in-kotlin
• https://issuetracker.google.com/77306535

It might be this has been the state of IntDef in Kotlin for a while...

I think the problem here is that you're using a default use site with the annotation; this means you have annotated the private field, not the getter or setter for that property!

Instead, you should use (in the @Insert annotation) a declaration like this:

    @get:OnConflictStrategy
    val onConflict: Int = OnConflictStrategy.ABORT

Once you do lint should enforce it.

(I looked at that other bug; it does not look like a bug to me; I'll add comments there.)

P.S. Default use sites continue to be a problem confusing developers. We have a potential lint check to help flag this in ag/15872109.

Ah default use sites! Not the first time it has bitten me! Thank you sooo much for the clarification. I didn't even consider it since @Insert being an annotation does not have fields, only getters, so I thought maybe Kotlin would place it in the right spot since it doesn't have to do the gymnastics to figure out whether to put it in a synthetic method, in the backing field, setter or getter. Anyway, I'll close this now, thanks again!