Appending to log.md drops the frontmatter the file carried
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 57/100
Research direction
Start in src/OKF4net with BundleConceptWriter.AppendLog and the ChangeLog rewrite path; trace how okf_append_log reads and writes log.md, then inspect the existing tests and goldens. Add coverage for logs with and without frontmatter, and preserve the frontmatter byte-for-byte or document a clear refusal. Done when both cases pass and existing goldens remain unchanged.
Written by the indexing model from the issue text.
Description
Area
src/OKF4net — BundleConceptWriter.AppendLog / ChangeLog rewrite of log.md; tool okf_append_log.
Problem
Appending an entry rewrites log.md through the §9 model and drops a frontmatter block the file carried. Content the author wrote is lost without warning. (Knock-on: the root index then lists the log by file stem under # Other.)
§9 does not give log.md a frontmatter, but the library's general rule is that unknown producer content survives a round-trip.
Acceptance
- An append to a
log.mdthat has a frontmatter keeps that frontmatter byte-for-byte (or the append is refused with a clear message — decide and document). - Tests for a log with and without frontmatter; goldens unchanged.
Found while building the #160 sample.
- Dominant language
- C#
- Stars
- 4
- Forks
- 1
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jchable/okf4net
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
.NET bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area/backend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
umbraco/Umbraco-CMS#24668 · 1 comment ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/extensions#7956 ·
Maintainers usually reply within 1 day