spelunker
spelunker copied to clipboard
Improved error handling
Certain errors are exposed to the client as network errors, even though they're not. Examples of these include GraphQL query violations and server side exceptions.
Example of requesting a non-existent field foo
in a specific tab:

It seems this is related to the Apollo client used by Spelunker under the hood: https://github.com/apollographql/apollo-client/issues/3386