Replies: 1 comment 4 replies
-
Good point, that example needs an update. Could you maybe file a PR? :) |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I have recently had to use queryFn to create a custom query that handles multiple async requests. I followed the example provided here.
When implementing I noticed that when we throw an error (if the first async requests fails) then we get the following warning ->
An Unhandled error occured processing a request for the endpoint... In the case of an unhandled error, no tags will be provided
The warning went away after we returned an object with the error property. I noticed that the documentation for the queryFn function also says that it should return an object with either the
data
orerror
property.What I was confused about was why the example provided for preforming multiple async requests with a single query throws an error Rather than returning an object with an error property (like the documentation for queryFn says to)?
Beta Was this translation helpful? Give feedback.
All reactions