useMutation - throwOnError triggering on each render about query HOT 3 CLOSED

like all our functional arguments to useQuery and useMutation, throwOnError is supposed to be a pure function that returns true or false, depending on which we will trigger error boundaries or not. Yes, we call this function a lot, but that shouldn't matter. If we were to memoize it, we would need to keep dependencies or you would need to memoize it with useCallback, and we'd need to store previous results etc. This is complex because you can close over values, like count, in this function. The only function where we do this is select on useQuery. For all other functions, it's just way easier to call them on each render.

i want to listen throwOnError

maybe you can explain what that means or why it matters that we call this function on every render ?

from query.

I've tried to write a custom error handler. It tries to handle the error.
If it can handle the error, it displays a modal with detailed information about the error and returns false on throwOnError, otherwise it returns true on throwOnError. However, this structure shows the error modal on every render.
How should I handle this case? It seems like throwOnError is not the right choice for my case.

from query.

throwOnError is not a function you can use to perform a side effect like rendering a modal. You should render a modal depending on the error field returned from useMutation or the onError callback.

from query.