The versioned (4 passages, no note) interface (21 passages, no note) through which a plugin (note: Plugin) contributes to the tool: readers (note: Reader) for file formats (16 passages, no note), converters (note: Converter), sources of entities (3 passages, no note) such as contract importers (note: Contract), inference methods (3 passages, no note), checks (note: Check), projections (4 passages, no note), user interface components (3 passages, no note), themes (note: Theme) and types (note: Type), each type a module (27 passages, no note) folder merged into the profile (note: Profile). A plugin exports a manifest (4 passages, no note) validated by the published schema (31 passages, no note), plugin.schema.json of the core (12 passages, no note) package (23 passages, no note), which is a JSON schema and not a contract the build imports (4 passages, no note), so this note (note: Note) declares none; it is declared in the configuration (note: Configuration) and loaded in order into a deterministic (3 passages, no note) registry (11 passages, no note). A plugin whose system (3 passages, no note) dependency (8 passages, no note) is missing disables itself with a finding.
Plugin API
Properties6
- Application
- Concordance command line
- Domain
- Quality
- Status
- valid
- Exposure
- internal
- Protocol
- internal
- Version
- 1
6 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapPlugin API
Neighbourhood map Plugin API
Distance1 hop
49 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- Entity pageScreenserves1
- EntityBusiness objectaccesses1
- LinkBusiness objectaccesses1
- ResourceBusiness objectaccesses1
- FindingBusiness objectaccesses1
- BuildBusiness objectaccesses2
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.