max-mapper / max-mapper/callback-hell
Can you show what your first example would look like "fixed"?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 858
- Forks
- 101
- PR merge metrics
- No merged PRs in 30d
Description
You showed an example (reading sizes of files) that seems very difficult to make better and even after following your steps, it is tough to read and understand. I would love to see the right way to do that.
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 by reading the first file-size example and the surrounding explanation in the repository’s documentation. Compare the current steps with the requested clearer presentation; done means the example shows an understandable fixed version of the file-size workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100