-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mastering async/await in JavaScript #3
Comments
Hey, I would love to work on this. I have written one already |
Hi @emee-dev, |
Ok let me do that |
Hey how can I do this, by PR ?? |
[x] You accept our Code of Conduct. Table of Contents
I have improved the article to be less AI like, for some reason Quillbot says my code snippets are AI generated Google doc |
@Rahulkhinchi03 could you please have a look at this? |
Hi @emee-dev, Could you please also add: difference between promise.all and promise.allSettled? |
Alright once I get home I would |
I have made a new PR with the differences |
Here is the link to the doc: https://docs.google.com/document/d/1WK4ho--WJk5u1v_gSy_hS65Ix9s6GRz9Ii-yUDiELZg/edit?usp=sharing |
Title
Mastering async/await in JavaScript
Brief
Write an article walking through how to efficiently handle async/await in JavaScript or TypeScript.
Guidelines:
Content Preparation:
Plagiarism Check:
Ensure your content is original by checking it for plagiarism. You can use a plagiarism checker like QUILBOT and share a screenshot showing the plagiarism percentage (ideally 25% max).
Collaboration & Avoiding Duplicates:
Claiming an Issue: If you'd like to write about a specific blog post topic, comment on the issue with a brief outline of your planned table of contents. This helps prevent two contributors from working on similar content.
Confirmation Checklist:
[ ] You accept our Code of Conduct.
[ ] My blog post is written in Google Docs and you have view permission.
[ ] I've included relevant visuals and examples to enhance understanding.
[ ] My content is original and AI-free. I've run a plagiarism check and can share the results.
[ ] I've commented on the issue with a table of contents outline (if applicable).
Once you've completed these steps, check the boxes and feel free to submit your blog post! We appreciate your contribution to the Treblle community.
The text was updated successfully, but these errors were encountered: