Remove the [Obsolete] path-based Bundle members (published obsolete in the release that ships #152)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
Research direction
Start by reading the members listed in the issue and the ObsoleteMembersTests tests; check the CHANGELOG migration note as well. Remove the listed path-based members and update their obsolete messages and the test requirement as described. Done when those members are removed, the tests reflect the new messages, and the CHANGELOG note explains the migration.
Written by the indexing model from the issue text.
Description
Decided on #152 (question 2): the members marked [Obsolete] … (#152) stay obsolete during the release that embeds #152 and are removed in the release after 0.8.0.
To remove: Bundle.Root, Bundle.IndexFiles, Bundle.LogFiles, Bundle.ParseErrors, Bundle.TryResolveResource, Bundle.ReadResourceText(string), OkfBundleTools.BundleRoot, BundleConceptWriter.BundleRoot.
Also: update the obsolete messages to "removed in the release after 0.8.0", relax ObsoleteMembersTests (no more "(#152)" requirement), CHANGELOG migration note. The sync RunComputation (obsolete since 0.7.0) goes with #152 itself, not here.
🤖 Generated with Claude Code
- 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