Closed bkahlert closed 1 year ago
Hi Björn. I did a little experiment, and learned that kapt tells the annotation processor about enum constants, but not the associated doc comments. This makes the scribe think the enum constants are undocumented, so it omits them from the JSON.
I suspect the fix for this issue would be in kapt. Getting the Kotlin team to look into it might be an uphill battle, since kapt is in maintenance mode and the future of annotation processing in Kotlin is KSP.
If someone knows a clever way to get enum constant doc comments from kapt, I can take another look. Until then, I'm afraid this is a "won't fix".
I'm using this annotation processor to bake in JavaDoc that get's picked up by an OpenAPI generation component. When I tried to add the enum constant JavaDocs to the OpenAPI document I can into the following problem:
The JavaDoc of enum constants doesn't seem to get processes / discovered when those are in Kotlin code. Though the class level JavaDoc get's processed.
Dependencies:
Kotlin enum
This creates the following json
MyEnum__Javadoc.json
:Now when I use the following Java enum, the enum constants get processed as expected:
MyJavaEnum__Javadoc.json
:Do you have any advice?