uber / NullAway / #615 / 1
93%
master: 93%

DEFAULT BRANCH: master
Ran
Files 47
Run time 5s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 89.307% (-0.03%) from 89.335%
#615.1

push

github-actions

web-flow 
Adds custom Nullable Annotation via Error Prone CLI flags (#522)

This PR adds the ability to configure additional custom `@Nullable/@Nonnull` annotations.

In particular, this adds the following configuration options to NullAway:

```
-XepOpt:NullAway:CustomNullableAnnotations=[...]
-XepOpt:NullAway:CustomNonnullAnnotations=[...]
```

Each of these options takes a comma-separated list of fully qualified annotation names, which NullAway should regard as nullable and non-null annotations (respectively), in *addition* to those it looks for by default. Neither configuration option is required when all relevant nullability annotations follow the conventions NullAway already expects (e.g. simple name `@Nullable` or `@NonNull` or any of our default supported annotations such as `@CheckForNull`).

During auto-annotation testing, we have encountered a few projects which are partially annotated with nullability annotations with different simple names than the conventional `@Nullable` or `@NonNull` (and recognized variations, such as `@NotNull`). For example, [LibGdx](https://github.com/libgdx/libgdx) uses [@com.badlogic.gdx.utils.Null](https://github.com/libgdx/libgdx/blob/master/gdx/src/com/badlogic/gdx/utils/Null.java). This is a custom nullability annotation which lives within the project itself and doesn't use the `@Nullable` simple name convention. Rather than explicitly encoding every such annotation in existence into our defaults, this PR allows supporting such cases with a simple configuration change.

3608 of 4040 relevant lines covered (89.31%)

0.89 hits per line

Source Files on job #615.1