The sentence (25 passages, no note) every finding carries saying what to change: add the note, fix the path, declare the domain. It comes from the catalogue of the check, the same for the build and the linter, and every finding line ends with the address of the documentation page of the check, whose "How to fix" section (note: Section) says more. The JUnit report (note: Forge report) shows the remediation with the message (22 passages, no note) so that a merge (27 passages, no note) request (31 passages, no note) reads it without opening the page.
Remediation
Properties3
- Application
- Concordance command line
- Domain
- Quality
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapRemediation
Neighbourhood map Remediation
Distance1 hop
48 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- CheckTermspecializes9
- FindingTermspecializes8
- Forge reportTermgeneralizes3
- LinterTermspecializes7
- NoteTermgeneralizes2
- SectionTermgeneralizes1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.