pholser / duly-noted Goto Github PK

When migrating one version of an annotation-based library to a new one there are a few features that could support that:

• Warn when deprecated annotations are being used
• Warn when unsupported annotations or attributes are being used
• Allow some form of translation from one (deprecated) annotation to one or several new ones, eg similar to Spring‘s aliases for attributes in another annotation

Handling annotations on Kotlin code from the Java side, ie without using Kotlin reflection comes with a few challenges:

• Current Kotlin versions require a compiler parameter to emit java annotations: "-Xemit-jvm-type-annotations"
• Annotations on parameters can be in two positions:

  fun myFunction(@Annotation1 param: @Annotation2 String) {}

  From a Java POV you may want to merge both into one.
• There are still bugs in Kotlin's annotation emission, e.g. https://youtrack.jetbrains.com/issue/KT-50042/Kotlin-produces-wrong-annotated-type-for-parameter-of-suspended-function-with-context-and-javaParameters-true, some of which could be hacked around.

I don't know if Kotlin-support is in scope for duly-noted, but it is interesting for libraries that aim at Kotlin compatibility.