Fork me on GitHub

I'm starting to look at Pathom3. I notice that resolver exceptions are swallowed. This is just an unfinished piece of p3 or is there some magic I should put into the environment so that exceptions are percolated?


i see that sm-get-with-stats provides a way of obtaining the exception


hello, its an unfinished piece, in Pathom I've seen different ways people need error information, the smart map for example, since it does a "per attribute" request, its possible to have the loud error mode, but for EQL the answer may vary. the first thing to consider is that "partial errors" are a big thing, since pathom has control over the process a lot can happen inside, and how to report the failure depends on your app needs. For instance, for front-end applications, its probably interesting to check at attribute level to see what worked and what failed. but for monitoring you may wanna know every error that happen. there is also the case of errors in OR branches, where an error may had happened, but another path worked, in this case, this should be reported as an error? sorry the big blog of text, I'm dumping the current thoughs on the error handling on Pathom, feedback and ideas are very welcome


so my guess its will end up with a few differnet API to handle the different cases, so its silent by default, but with accessors for different needs


No worries. I appreciate the insight. I certainly see the need for multiple approaches for errors.