repowise-dev / repowise-dev/repowise
[Feature] Documentation coverage for specific folders
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.7k
- Forks
- 711
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 439
Description
Problem
It would be nice to have ability to set coverage for specific folders.
Fox example I have business logic "core" where I want 100% docs coverage.
And there maybe some folders, which I not considered as important at first, but later I want to increase there coverage
Proposed Solution
Some flag in init and update to have specified coverage for fodlers like:
--folder-coverage "./src/core=1"
Contributor 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.
Research direction
Start by locating the init and update entry points and the existing documentation coverage calculation. Trace how coverage thresholds are configured and reported before deciding where the proposed --folder-coverage "./src/core=1" option belongs. Done means folder-specific targets can be configured for both commands and are applied consistently to coverage results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100