<@UDVMV4NBU> Initially, I started having to use th...
# micronaut
d
@Graeme Initially, I started having to use the javax APIs because Micronaut does not have a way to get annotations applied to enum entries (or entry elements at all, rather than just names). There's also third-party libraries - I started using kotlin-metadata, which has at least a partial dependency on
ProcessingEnvironment
and it's surprising that I need to jump through hoops to make existing tools work. While I found the Micronaut support for annotation processing to be well-integrated, I think the type-safe native APIs are a bit cleaner, and I'm not sure why I'd want to use the Micronaut APIs if I'm writing a tool that will only run on Kotlin at compile-time. Of course I could write a standalone annotation processor, but then there is no easy way to access Micronaut features (and things like annotation stereotypes) that I am aware of