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

Update sentence in Unhandled rejections

Browse source
This commit is contained in:
Peter Keller 2018-10-01 18:25:55 -04:00
parent c5ca14fdcb
commit b82136a94c
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
6-async/03-promise-chaining/article.md
View file

@ -635,7 +635,7 @@ new Promise(function() {
In case of an error, the promise state becomes "rejected", and the execution should jump to the closest rejection handler. But there is no such handler in the examples above. So the error gets "stuck". In case of an error, the promise state becomes "rejected", and the execution should jump to the closest rejection handler. But there is no such handler in the examples above. So the error gets "stuck".
In practice, that's usually because of the bad code. Indeed, how come that there's no error handling? In practice, that's usually because of the bad code. Indeed, how come there's no error handling?
Most JavaScript engines track such situations and generate a global error in that case. We can see it in the console. Most JavaScript engines track such situations and generate a global error in that case. We can see it in the console.