One of the ways a plugin adds to the tool, named by a key of its manifest: readers (a reader per file format), converters (a converter), sources (a source of entities such as a contract import), inferenceMethods (a method that produces links), checks (a check with its identifier, severity, remediation and page), projections (a rendering of the model), uiComponents (a bundle a slot loads on demand), themes (a theme with components by slot) and types (a type module per folder, merged into the profile). The data around each contribution is validated by the plugin schema (31 passages, no note); the functions are called with their input and an injected context (note: Passage), and never read the clock or the network on their own.
Contribution point
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 mapContribution point
Neighbourhood map Contribution point
Distance1 hop
62 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ContractTermspecializes1
- ConverterTermspecializes2
- ReaderTermspecializes4
- Type moduleTermspecializes1
- SlotTermspecializes1
- ThemeTermspecializes2
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.