Is there a better way to manually setError on a query?

[bruno-vinicius]

I was messing around the query object and found a dispatch on it, so i make a
query.dispatch({ type: 3, error: { foo: "bar" } }); (3 in this case is the enum value of ActionType.Error)
and it worked. But i don't know if this is "clean enough".

[TkDodo]

can you elaborate a bit what your use-case would be? Why do you manually need to set it to error?

[bruno-vinicius]

It's a bit odd i know, but is a kind-of-authorization flow with the first request is given an error and the next request (this one that "resolves" the authorization) return the result of the first. So my solution was something like "hold" error state of the first request, make the second, and resolve or reject in case of a new error, the first one. I make this with another library (digging the code and use undocumented features) so was think in addressing this first before "full switch" to react-query.

[TkDodo]

The answer to many/most questions is “custom hooks” 😅

[bruno-vinicius]

Strong agree 😄 !!!

[bruno-vinicius]

I'm marking this thread as the answer but it puts my name on it instead of yours. 😢

[TkDodo]

Yes because you started the thread 🤷‍♂️. I don’t care as long as people will find the right answer👍

[bruno-vinicius]

I think i found a well-suited solution, i can wrap the base fetch on another Promise and pass the resolve and reject to be manually fired by another (in this case top-leve) place of my code (using Context). So i can make another request and resolves or reject the first one with a new data or error. Thanks for the help and the inspiration.

[bruno-vinicius]

queryCache.setQueryData solve the "resolve" part, but i was thinking if was useful to have an error one.