Caleb Cushing

https://docs.oracle.com/javase/specs/jls/se12/html/jls-9.html#jls-9.7.4

Yeah, type annotations aren't that common, honestly I only see it related to `@Nullable` other nullity-related annotations. To be honest you could just support it via checks for a handful...

ironic you should mention error prone, because that's what's checking this error ``` /home/xeno/IdeaProjects/pm/backend/module/util/model-graph/src/testFixtures/java/com/xenoterracide/ppm/util/modelgraph/Neo4jExtension.java:18: error: [AnnotationPosition] @Nullable is a TYPE_USE annotation, so should appear after modifiers and directly before the...

https://errorprone.info/bugpattern/AnnotationPosition

I can just disable it 🤷🏻‍♂️, I don't have more arguments than these ;)

yeah, but that's kinda painful to do for every Nullable annotation

perhaps not moving annotations out of that position would be a good workaround per #548 I don't notice this problem with getter/setters, so what's being done there?

because, the first is an external library that should not be used like that, and the latter is a lot of code that I want warnings for while we fix...

perhaps a better solution, at least in my case would be to have an `[import/no-internal-from-external-modules]` rule... which could potentially use the rule that defines what's internal

bad, no argument, but progressive migration ftw.