Development record
ultra-v0.6.8 below-cap reuse-5: the memory frontmatter parser (frontmatterOpenIndex in internal/core/memory/yaml.go) trims lines with strings.TrimSpace, which does not strip U+FEFF, while the record-lint parser uses frontmatter.TrimBOM, so a BOM-led memory page is a page with frontmatter to record-lint and a page without it to memory. Pre-existing, not introduced by the reviewed slice.
issueresolvedminoriss-2608291814565781
ultra-v0.6.8 below-cap reuse-5: the memory frontmatter parser (frontmatterOpenIndex in internal/core/memory/yaml.go) trims lines with strings.TrimSpace, which does not strip U+FEFF, while the record-lint parser uses frontmatter.TrimBOM, so a BOM-led memory page is a page with frontmatter to record-lint and a page without it to memory. Pre-existing, not introduced by the reviewed slice.
Grounds
- pursued: every memory frontmatter reader shares frontmatterOpenIndex, so one strip there aligns them with record-lint; a BOM-led page that textOpensFrontmatter, parseFrontmatter, splitFileFrontmatter or frontmatterKeyLine still reads as frontmatter-less would show it wrong
Frontmatter
| id | iss-2608291814565781 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608291814565781-memory-frontmatter-parser-is-bom-unaware.md
open on GitHub ↗ · commit history ↗