microsoft / microsoft/RecursiveExtractor
Clean up Documentation and Interfaces
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 220
- Forks
- 35
- Avg merge
- 20d 1h
- Merged PRs (30d)
- 1
Description
Extractor.cs in particular has calls that have duplicative options - passing both an extractor options and the allow/deny filters.
Many extractors also have not had their documentation comments updated.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with Extractor.cs and identify calls that pass both extractor options and allow/deny filters. Then review the extractors whose documentation comments are outdated; done means the duplicate option passing is cleaned up and the relevant comments are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100