typetools / typetools/checker-framework
Generate report file from analysis.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
Currently, Checker Framework outputs all the warnings and errors to the console.
When using a build system like maven or gradle, the order of output can vary (see known bug with maven).
Checker Framework should generate a parsable report file which can be easily extended to create universal suppression systems, etc.
Currently, at Checkstyle, we use a custom suppression model built with groovy, which parses the output and checks the .xml suppression file.
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 by reviewing the current Checker Framework console output and the linked Checkstyle .ci/checker-framework.groovy suppression model. Determine the report format and generation path needed to replace parsing console output; done means a parsable report file is produced for analysis results and supports the intended suppression workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100