Deprecated API
Contents
-
Deprecated InterfacesInterfaceDescriptionuse
Matcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.useMatcher<ExpressionTree>instead of referring directly to this type.
-
Deprecated Annotation InterfacesAnnotation InterfaceDescriptionthe correctness of this annotation is not enforced; it will soon be removed.the correctness of this annotation is not enforced; it will soon be removed.
-
Deprecated MethodsMethodDescriptionuse
IncompatibleModifiers.modifier()insteaduseRequiredModifiers.modifier()insteadpreferBugCheckerRefactoringTestHelper.addInputLines(String, String...). Declaring tests in the same file using text blocks is more readable, as it encourages writing small, focussed tests.preferBugCheckerRefactoringTestHelper.ExpectOutput.addOutputLines(String, String...). Declaring tests in the same file using text blocks is more readable, as it encourages writing small, focussed tests.this is a no-op that will be removed in the futureuseBugChecker.isSuppressed(Tree, VisitorState)insteaduseBugChecker.isSuppressed(Symbol, VisitorState)insteadWellKnownMutability.getKnownImmutableClasses()is clearer if you're dealing with this specific class.WellKnownMutability.getKnownMutableClasses()is clearer if you're dealing with this specific class.preferCompilationTestHelper.addSourceLines(String, String...). Declaring tests in the same file using text blocks is more readable, as it encourages writing small, focussed tests.prefer referring to empty fixes usingSuggestedFix.emptyFix().useMatchers.isNonNullUsingDataflow()instead.useMatchers.isNullUsingDataflow()instead.The implementation uses javac internals to pretty-print the signatures, and the signature format is not well-specified.IfannotationClasscontains a member that is aClassor an array of them, attempting to access that member from the Error Prone checker code will result in a runtime exception. Instead, operate ongetSymbol(tree).getAnnotationMirrors()to meta-syntactically inspect the annotation. Note that this method (and thegetSymbol-based replacement suggested above) looks for annotations not just on the given tree (such as aMethodTree) but also on the symbol referred to by the given tree (such as on theSymbol.MethodSymbolthat is being called by the givenMethodInvocationTree). If you want to examine annotations only on the given tree, then useASTHelpers.getAnnotations(Tree)(or a direct call to agetAnnotationsmethod declared on a specificTreesubclass) instead.IfannotationClasscontains a member that is aClassor an array of them, attempting to access that member from the Error Prone checker code will result in a runtime exception. Instead, operate onsym.getAnnotationMirrors()to meta-syntactically inspect the annotation.TODO(ghm): delete after a JavaBuilder releasecom.google.errorprone.util.ASTHelpers.hasAnnotation(Tree, Class<? extends Annotation>, VisitorState) preferASTHelpers.hasAnnotation(Symbol, String, VisitorState)to avoid needing a runtime dependency on the annotation class, and to prevent issues if there is skew between the definition of the annotation on the runtime and compile-time classpathspreferASTHelpers.hasAnnotation(Symbol, String, VisitorState)to avoid needing a runtime dependency on the annotation class, and to prevent issues if there is skew between the definition of the annotation on the runtime and compile-time classpathsuse TargetType.targetType directly
-
Deprecated ConstructorsConstructorDescriptionIf VisitorState is needed, use
VisitorState.createForUtilityPurposes(Context), otherwise just use utility methods in ASTHelpers that don't need VisitorSate.Use the equivalent factory methodVisitorState.createForCustomFindingCollection(Context, DescriptionListener).Use the equivalent factory methodVisitorState.createConfiguredForCompilation(Context, DescriptionListener, Map, ErrorProneOptions).
-
Deprecated Annotation Interface ElementsAnnotation Interface ElementDescriptionuse
IncompatibleModifiers.modifier()insteaduseRequiredModifiers.modifier()insteadthis is a no-op that will be removed in the future