max-mapper / max-mapper/callback-hell

async

Open
#32 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
858
Forks
101
PR merge metrics
No merged PRs in 30d

Description

I think more emphasis could be done on how to rewrite code from callback hell style to async style, also, more effor could be made in order to explain why async is a good idea, including async examples and await try catch stuff.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the repository's current async JavaScript material and identify where callback-to-async guidance and examples belong. Add explanations of the benefits of async style, rewrites from callback hell, and async/await examples covering try/catch; done means these topics are clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.