Problem:
TypeScript errors are typed "unknown".
Solution:
Throw custom errors. They're easy to inspect.
How:
1. Create an ErrorBase class.
2. Create an instance ErrorBase for each feature and specify the feature's potential errors.
#typescript
TypeScript errors are typed "unknown".
Solution:
Throw custom errors. They're easy to inspect.
How:
1. Create an ErrorBase class.
2. Create an instance ErrorBase for each feature and specify the feature's potential errors.
#typescript
Note that the base class also enforces including a cause property, so the original error's info remains available.
Here's why cause is handy:
Here's why cause is handy:
https://twitter.com/housecor/status/1608795552644476928
I've used a similar pattern on previous projects. It's quite helpful.
Credit to @KolbySisk who wrote a post that gave me the idea of creating the base class.
See his excellent post for more info on creating custom errors: engineering.udacity.com/handling-error…
Credit to @KolbySisk who wrote a post that gave me the idea of creating the base class.
See his excellent post for more info on creating custom errors: engineering.udacity.com/handling-error…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
