`AddNullMarkedToClass` has no documentation

[uhafner]

In 2.46.0 I get a lot of new warnings due to AddNullMarkedToClass. The link resolves to https://errorprone.info/bugpattern/AddNullMarkedToClass, which is empty. It would be helpful to get some instructions for this rule.

I marked all my classes using a package directive, so I have no idea what I am making wrong:

@DefaultAnnotation(NonNull.class)
package edu.hm.hafner.util;

See https://github.com/uhafner/codingstyle/runs/59898174755 and uhafner/codingstyle#1714.

[cushon]

AddNullMarkedToClass should be disabled by default, are you using the default configuratino, or did you pass flags to enable that refactoring?

error-prone/core/src/main/java/com/google/errorprone/scanner/BuiltInCheckerSuppliers.java

Line 1196 in eca0f3c

AddNullMarkedToClass.class,

[uhafner]

I am using the default configuration, as far I can understand:
https://github.com/uhafner/codingstyle/blob/9b6151a4e9e63b17324052d50ad053c6feb67765/pom.xml#L591-L705

[uhafner]

Sorry, I activated: -XepAllDisabledChecksAsWarnings

[uhafner]

So I am closing this issue. Works now: uhafner/codingstyle#1714

[cushon]

Sorry, I activated: -XepAllDisabledChecksAsWarnings

Thanks, that makes sense. This check is intended as an optional refactoring for code that wants to use the jspecify.dev org.jspecify.annotations.NullMarked annotation. It isn't something we're planning to enable by default or recommend for all users of Error Prone.

I'll see about getting the docs updated to explain the purpose of the check.

If you want to use -XepAllDisabledChecksAsWarnings and this check isn't applicable to your codebase, I'd suggest just turning it off: -XepAllDisabledChecksAsWarnings -Xep:AddNullMarkedToClass:OFF