A check the linter computes on one repository (note: Knowledge repository) alone, without the network and without the rest of the model: encoding, frontmatter (note: Frontmatter), identifiers (note: Identifier) and internal links (note: Link). The lint package (3 passages, no note) lists them as LOCAL_CHECKS. For these checks the linter (4 passages, no note) and the build (note: Build) produce the same findings on the same repository, wording (4 passages, no note) included; a parity (note: Linter and build parity) test on the golden corpus and on the faulty corpus (note: Corpus) holds them to it, and the JSON report (47 passages, no note) of the linter (note: Linter) repeats the list so that a forge report (note: Forge report) says what was checked.
Local check
Properties4
- Application
- Concordance command line
- Domain
- Quality
- Status
- valid
- Broader term
- quality/checks/check.md
4 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapLocal check
Neighbourhood map Local check
Distance1 hop
42 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ModelTermspecializes2
- CheckTermspecializes4
- Global checkTermgeneralizes1
- Link checksTermgeneralizes1
- FindingTermspecializes3
- Excluded fileTermspecializes1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.