jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Update article.md

Browse source 
"chapter" -> "article" 2x
This commit is contained in:
Peter Roche 2020-02-11 22:19:54 -07:00 • committed by GitHub
parent 425a0af8be
commit 837f7ab024
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
1-js/11-async/07-microtask-queue/article.md
View file

@ -54,7 +54,7 @@ Now the order is as intended.
## Unhandled rejection
Remember the `unhandledrejection` event from the chapter <info:promise-error-handling>?
Remember the `unhandledrejection` event from the article <info:promise-error-handling>?
Now we can see exactly how JavaScript finds out that there was an unhandled rejection.
@ -109,4 +109,4 @@ So `.then/catch/finally` handlers are always called after the current code is fi
If we need to guarantee that a piece of code is executed after `.then/catch/finally`, we can add it into a chained `.then` call.
In most Javascript engines, including browsers and Node.js, the concept of microtasks is closely tied with the "event loop" and "macrotasks". As these have no direct relation to promises, they are covered in another part of the tutorial, in the chapter <info:event-loop>.
In most Javascript engines, including browsers and Node.js, the concept of microtasks is closely tied with the "event loop" and "macrotasks". As these have no direct relation to promises, they are covered in another part of the tutorial, in the article <info:event-loop>.