re-graph
re-graph copied to clipboard
oliyh
Default error handler
Rather than having possibly duplicated error handling logic in every response handler it might be useful to have a catch-all handler
It appears that this was implemented for subscriptions without any possibility to override the default error handler with a customised one: https://github.com/oliyh/re-graph/blob/78ac8b55dfbf3a0613152bab2f9a664e7e14274a/src/re_graph/internals.cljs#L148-L161
Hi @urzds
The code you link to is specifically for "general" errors, not errors relating to specific queries. I don't know when these might happen, I've not seen them using lacinia-pedestal, but I don't think it's a common use case to be able to handle it (please correct me if I'm wrong, and if you are seeing this specific case - I'd like to know what the scenario is).
If a query has an error the message from the server will be of type "data" which contains errors (see this issue). All messages are passed to your callback handler, it is up to the callback handler to check if there are errors in the response and do something appropriate. It was this use case I had in mind when I wrote this issue - that all handlers might check for errors and then handle it the same way, which would cause duplication.
I am creating a ::re-graph/subscription and when I try to query non-existing fields, I see this on the browser console:
GraphQL error for <subscription-id>: Cannot query field `idXX' on type `<TypeName>'.
At least Lacinia 0.29.0 / Lacinia Pedestal 0.10.0 sends errors for subscriptions this way. (I could not quickly figure out how the GraphQL spec requires this case to be handled). Since re-graph does not pass on these errors, my application has no way of handling this itself and hence cannot display any kind of error message. Could of course also be a bug in Lacinia...
It's a pity that we cannot specify the custom error handler for cases when the type is actually a known error - in cases like when the backend is throwing e.g. "credentials expired" errors.
