Uncaught API Exceptions

Is it intended that all uncaught API exceptions are captured in the graphql response? Are there good ways to bubble up these uncaught exceptions in a way that doesn’t require drilling into graphql response in the network tab and expanding down to the exception stack trace?

At the end of the day it’s a minor annoyance, but after doing it a few dozen times, it adds up.

This is by no means a complaint - just curious if I’m missing an obvious way to get these quickly!

1 Like

Thanks for bringing this up. This has hit me a bunch of time and I brushed it off as something that I would like to eventually improve.

I think we can modify the way that the Cell handles these so that they’re visible during development (Just like any uncaught exception would be.)

I’ve opened up an issue over here: https://github.com/redwoodjs/redwood/issues/535

1 Like