Bound mutate doesn't trigger SWRConfig onError

[andersnylund]

I am trying to create a "global" error handling so that if either an useSWR or an mutate fails a notification will be shown. However, I am not able to get the bound mutate to cause an error that would be caught be the onError-handler in the SWRConfig that wraps the application.

I have a reproduction here: https://codesandbox.io/s/elegant-herschel-n59qk

As you can see the error thrown inside the fetcher in useSWR will cause the onError handler to log the error in the console. However the error thrown inside the mutate is not showing up in onError. However the error-object returned from useSWR call is returning the error that was caused by the mutate.

Is it possible to get the errors from bounded mutations to show up in onError-handler?

[agatsumayuki]

I have the same problem here. Is there any solutions to this problem?

[cellulosa]

any hint?

[piassi]

+1 also having this issue at the moment.

[daveycodez]

Sheittttt guess I gotta make a custom SWR Error Context implementation ;/

EDIT :

My solution is just to add

const { onError } = useSWRConfig()

Then

try { mutate() } catch (error) { onError(error) }

Kinda janky and not ideal D: maybe put it directly into your fetcher for mutates and catch it there.