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!
