Auto-stamped generated.by carries the spec version (okf4net/0.2), not the producer version (§7)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 56/100
Research direction
Start at BundleConceptWriter.DefaultProducerActor in src/OKF4net/BundleConceptWriter.cs and check how the assembly informational version is exposed; OkfContextProvider also uses this default. Add a test for the actor version, then review goldens and MachineOutputTests for the old okf4net/0.2 value. Update the CHANGELOG; any semantic golden change needs arbitration under tests/fixtures/README.md.
Written by the indexing model from the issue text.
Description
Area
src/OKF4net — BundleConceptWriter.DefaultProducerActor (BundleConceptWriter.cs:248), also used by OkfContextProvider.
Problem
Auto-stamped writes record generated.by: okf4net/0.2. The default actor is "okf4net/" + OkfSpec.Version — the spec version. §7 defines the actor convention as <producer>/<version> for agents and tools, i.e. the producer's own version (okf4net/0.8.0), which is what tells a reader which build wrote the content.
Acceptance
- The default actor is
okf4net/<library version>(from the assembly's informational version, without the+<commit>suffix), with a test. - Check goldens and
MachineOutputTestsfor any expectation ofokf4net/0.2; a golden diff here is semantic (a written document) and needs arbitration pertests/fixtures/README.md. - CHANGELOG entry (the stamp written by the library changes).
Found independently while writing the #159 sample and the #174 tutorials.
- 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