issues
The issues a repository keeps as code, as records
Applies to: Project and issues. The open work of a library as data: its issues, their goals and what would close them.
Written in commons/data/models/issues/mod.ts:149. Requires nothing. 6 concepts, 9 code lists.
Diagram source
flowchart LR
issue_engine -->|issue| issue
issue_evidence -->|issue| issue
issue_goal -->|issue| issue
issue_link -->|issue| issue
issue_link -->|target| issueConcepts
| Concept | Definition | Attributes | Written in |
|---|---|---|---|
issue | One known weakness of a library or a module, as the code of the repository says it | 18 | commons/data/models/issues/mod.ts:75 |
issueEngine | An engine an issue is about | 2 | commons/data/models/issues/mod.ts:114 |
issueEvidence | A piece of evidence of an issue | 4 | commons/data/models/issues/mod.ts:116 |
issueGoal | A goal an issue is held against | 2 | commons/data/models/issues/mod.ts:112 |
issueLink | How an issue is related to another of its scope | 2 | commons/data/models/issues/mod.ts:122 |
issueSync | One synchronisation of the records with the code, kept as a ledger | 9 | commons/data/models/issues/mod.ts:130 |
Code lists
| Code list | Definition | Codes |
|---|---|---|
issueEvidenceKind | What kind of evidence | 5 |
issueGoal | What the library is meant to be | 8 |
issueLinkKind | How two issues are related | 3 |
issuePresence | Whether the code still has the issue | 2 |
issuePriority | When it is to be done | 3 |
issueSeverity | How bad an issue is | 4 |
issueSize | How much work the fix is | 5 |
issueStatusKind | Where an issue is | 7 |
issueSyncOutcome | What a synchronisation did | 2 |