Thanks for attaching this link for reference. ๐
The way this would be super helpful is in deeply nested functions with chained errors.
Like if we have mutiple try catch block inside a deeply nested function so we pass the string as the purpose of that block and cause as the argument of catch block. For example:
functiondeeplyNested(){try{// outer block logic.letappData=[{...}]// app data array parsing.appData.map((data)=>{try{// ยทยทยท}catch(error){thrownewError(`While processing ${data}`,{cause:error});}});}catch(error){throwError('Error while processing outer block',{cause:error});}}
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ah, mystery solved!
2ality.com/2021/06/error-cause.html
It's for chaining errors - like the "inner exception" you have in many other languages.
Because you can throw anything in JS, the property type isn't specified as Error - but the intention is similar.
Thanks for attaching this link for reference. ๐
The way this would be super helpful is in deeply nested functions with chained errors.
Like if we have mutiple try catch block inside a deeply nested function so we pass the string as the purpose of that block and cause as the argument of catch block. For example: