Missing documentation/explanation for tilelive-copy options
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 540
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
The "best" source of information about how tilelive-copy works is the source itself. The --help and git tree don't have many details. Some flags like --concurrency could use some explanation about how it works and --parts should have a description at the very least...
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 with the tilelive-copy source and its --help output, then compare the documented flags with the git tree. Explain how --concurrency works and add at least a description for --parts; done means the key options are understandable without reading the source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100