okfgen: the pruning guard compares scope flags, not the scope rule
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
Research direction
Start by reading BundleWriter and the manifest scope handling, then run dotnet test producers/OkfProducer.sln. The issue proposes storing a scope-rule identifier alongside scope so the existing pruning guard detects rule changes, but notes that changing the manifest format requires a compatibility decision. Done means rule changes trigger the guard without silently pruning concepts.
Written by the indexing model from the issue text.
Description
Extracted from ROADMAP.md (producers/OkfProducer follow-ups).
BundleWriter refuses to prune when the previous run covered a wider scope. It decides this by comparing the flags recorded in the manifest, so it is blind to a run whose flags are identical but whose rule narrowed.
Measured: a bundle generated before scope moved to effective visibility was regenerated with the same flags. It lost five concepts and the guard stayed silent.
The producer now prints a note when it caps a public member at an internal container, which covers today's only case.
General fix: record a scope-rule identifier beside scope in the manifest, so that the existing guard fires on a rule change. This changes the manifest format, which is a compatibility decision of its own.
The producer is outside CI: run dotnet test producers/OkfProducer.sln.
- 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