Handling Errors in Effect: Failures vs. Defects
Failures vs. Defects question:
BullMQ has a special Error called WaitingForChildrenError.
this is typically thrown when adding a child job and the parent should wait for children to be done before resuming work. I created a
The problem I see is that this tag could be caught at some level other than root level (where it is supposed to be caught). If I use a defect, nobody can catch and re-map the error that needs to stay the same. Would this justify making a defect out of it for the reason that it mustn't be handled somewhere in the chain?
BullMQ has a special Error called WaitingForChildrenError.
this is typically thrown when adding a child job and the parent should wait for children to be done before resuming work. I created a
Data.TaggedErrorWaitingForChildrenErrorEffect.failEffect.dieThe problem I see is that this tag could be caught at some level other than root level (where it is supposed to be caught). If I use a defect, nobody can catch and re-map the error that needs to stay the same. Would this justify making a defect out of it for the reason that it mustn't be handled somewhere in the chain?
Similar Threads
Was this page helpful?
