Development record
readingitem.ResolveOccasion takes an issues root and, for an itd-N occasion, recovers the repository root by suffix-stripping .abcd/work/issues off it, while its one caller (intent/condition.go) joins that suffix on only for it to be stripped; the lookup then builds a full recordid.NewResolver over every record family (intents, specs, issues, ADRs) to find one intent, so an unreadable spec store refuses an intent occasion. The leaf should take the repository root and look up the intent store alone.
issueresolvedminoriss-2609251052591014
readingitem.ResolveOccasion takes an issues root and, for an itd-N occasion, recovers the repository root by suffix-stripping .abcd/work/issues off it, while its one caller (intent/condition.go) joins that suffix on only for it to be stripped; the lookup then builds a full recordid.NewResolver over every record family (intents, specs, issues, ADRs) to find one intent, so an unreadable spec store refuses an intent occasion. The leaf should take the repository root and look up the intent store alone.
Grounds
- pursued: an intent occasion resolves from the repository root with no suffix arithmetic and with an unrelated family's store unreadable; TestResolveOccasionReadsOnlyTheIntentStore and TestLookupOneReadsOnlyTheIdsFamily would fail if either returned
Frontmatter
| id | iss-2609251052591014 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609251052591014-readingitem-resolveoccasion-takes-an.md
open on GitHub ↗ · commit history ↗