typetools / typetools/checker-framework
Enforce @TargetLocations annotation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
If qualifier Q has a @TargetLocations meta-annotation and the programmer writes @Q at any location that is not listed in Q's @TargetLocations meta-annotation, then the Checker Framework should issue a warning. This warning may be suppressed (say, for making default annotations explicit in test cases).
(Issue ported from #515 which had become cluttered with other discussion.)
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
No source file, test, or entry point is named. Start by locating the Checker Framework handling for @TargetLocations and qualifier annotations, then trace where annotation-use locations are validated. Done means an invalid @Q location produces a suppressible warning while listed locations remain accepted.
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
- Mostly clear
- Newbie friendliness
- 25/100