Documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
Research direction
No documentation file or test is named in the issue. Review the repository structure and existing sample-sizer usage first, then document when to use it and how to use it, with a more polished presentation. Done means all three checklist items are addressed.
Written by the indexing model from the issue text.
Description
- When to use sample-sizer
- How to use sample-sizer
- make it look pretty
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
More from mapbox/sample-sizer
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapbox/sample-sizer#3 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mapbox/sample-sizer#2 ·
All issues in mapbox/sample-sizer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100