Makes sense. There isn't really anything limiting,...

# micronaut

[damian]

Makes sense. There isn't really anything limiting, as I like using the TypeElementVisitor API as an entry point (since it handles things like annotation stereotypes, etc automatically), but as of right now I'm also casting to JavaVisitorContext and pulling out ProcessingEnvironment reflectively to be able to do some pure-java processing at the same time. I'm thinking something analogous to Element.nativeType for VisitorContext (e.g. VisitorContext.nativeEnvironment, where JavaVisitorContext.nativeEnvironment would return the ProcessingEnvironment) might be a potentially useful escape hatch for when it's needed. I will think about it some more what the ideal situation would be and report back (perhaps with PRs) 🙂