Support @MonotonicNonNullDecl by default as an excluded field annotation
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 4.1k
- Forks
- 370
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 68
Description
Do you plan to support @MonotonicNonNullDecl? Recently I added this annotation to guava (https://github.com/google/guava/blob/master/guava/src/com/google/common/reflect/TypeToken.java#L105)
Or more generally, do you support the nullness annotations of the checker framework?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced Guava TypeToken.java location to understand how @MonotonicNonNullDecl is used, then inspect NullAway's existing handling of excluded field annotations. Determine whether support should cover this annotation specifically or Checker Framework nullness annotations more broadly, and add focused coverage demonstrating the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100