You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to put up a feature request for support for TanStack Query v5 which makes defaultPageParam mandatory in useInfiniteQuery and exposes pageParam and direction in QueryFnContext.
If there might be interest in supporting it, I would be happy to offer some help too.
The text was updated successfully, but these errors were encountered:
Additionally, I am having some issues with useQueries on v5. Queries that I define through query-key-factory that work fine with useQuery seem to have typing issues with useQueries. See screenshots:
Hey everyone, thank you for the suggestion in adding support for v5 new APIs, unfortunately I've been very busy lately without being able to put too much work into new features (the type system is extremely complex by now, so it takes some effort to add new things and not break things). I'll put this on my radar, but can't guarantee something in the near future.
Also, since there are some changes in APIs for V5, it would probably make sense to have a new major version with support only for v5 instead of adding here and being incompatible with a lot of folks that are still using V4.
@gbyesiltas from what I can see in your TS errors, the queries for useQueries expect some kind of MaybeRef that is making it incompatible with the normal function declaration. I'll need to understand the different signature it is expecting and see how we can make the type declaration compatible with its signature
Hi,
I wanted to put up a feature request for support for TanStack Query v5 which makes
defaultPageParam
mandatory inuseInfiniteQuery
and exposespageParam
anddirection
in QueryFnContext.If there might be interest in supporting it, I would be happy to offer some help too.
The text was updated successfully, but these errors were encountered: