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

minor

Browse source
This commit is contained in:
Ilya Kantor 2017-09-17 19:44:37 +02:00
parent 8b4cd384b3
commit 9bf0153f70
2 changed files with 138 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
1-js/08-error-handling/2-custom-errors/article.md
View file

@ -224,7 +224,7 @@ The code which calls `readUser` should handle these errors. Right now it uses mu
Often the answer is "No": the outer code wants to be "one level above all that". It wants to have some kind of "data reading error". Why exactly it happened -- is often irrelevant (the error message describes it). Or, even better if there is a way to get error details, but only if we need to.
So let's make a new class `ReadError` to represent such errors. If an error occurs inside `readUser`, we'll catch it there and generate `ReadError`. We'll also keep the reference to the original error in the `cause` property. Then the outer code will only have to check for `ReadError`.
So let's make a new class `ReadError` to represent such errors. If an error occurs inside `readUser`, we'll catch it there and generate `ReadError`. We'll also keep the reference to the original error in its `cause` property. Then the outer code will only have to check for `ReadError`.
Here's the code that defines `ReadError` and demonstrates its use in `readUser` and `try..catch`: