On Mon, Dec 28, 2015 at 10:38 AM <[email protected]> wrote: > Hi, > > I have a detector that extends the implements createJavaVisitor and the > AstVisitor returned by it has visitClassDeclaration method. > > If I implemented applicableSuperClasses in my detector, the > createJavaVisitor is correctly called, for each sub-classes listed, > but the visitClassDeclaration was *not* called. > > This is a intentional feature (why?) or a bug? >
Yeah, that's working as intended right now; instead of creating a visitor, just implement the visitClass method which is called directly, providing you both the AST node as well as the ResolvedClass. (I plan to revisit this as part of a bunch of larger changes around detector registration to make it easier to opt into individual callbacks.) -- Tor -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
