We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Writing code like this will produce a compiler error:
useQuery({ queryKey: ['my-query'], queryFn(ctx) { return { foo: 1 } }, refetchInterval(data) { return 10000 }, select(data) { return data.foo }, })
Removing data from refetchInterval makes it go away. This seems to be a conflict between the type change in select and the usage of data in callbacks.
data
refetchInterval
#5309
This should work
Every time
No response
Everywhere
react-query
4.29.4
4.8.3-5.x
The text was updated successfully, but these errors were encountered:
This was initially picked up in trpc/trpc#4234 but is actually a react-query issue as demonstrated by #5309
Sorry, something went wrong.
Looks like order in the object matters, this fixes the compile error:
useQuery({ queryKey: ['my-query'], queryFn(ctx) { return { foo: 1 } }, select(data) { return data.foo }, // move this below refetchInterval(data) { return 10000 }, })
Is most likely related to microsoft/TypeScript#53018
if you want, please contribute a section to the docs on the typescript page that explains this limitation
No branches or pull requests
Describe the bug
Writing code like this will produce a compiler error:
Removing
data
fromrefetchInterval
makes it go away. This seems to be a conflict between the type change in select and the usage of data in callbacks.Your minimal, reproducible example
#5309
Steps to reproduce
#5309
Expected behavior
This should work
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
Everywhere
Tanstack Query adapter
react-query
TanStack Query version
4.29.4
TypeScript version
4.8.3-5.x
Additional context
No response
The text was updated successfully, but these errors were encountered: