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
Thanks for the new queryOptions, it's really useful for prefetching queries in the route loaders. However I have a small issue with queryOptions. The third parameter seems required, even when no parameters is expected.
vs
Reproduction
Last Typescript version (don't know if it matters), an endpoint in the openapi which doesn't need any parameter.
queryOptions should behave the same than other hooks.
Expected result
queryOptions always requires a third parameter (an empty object do the trick however).
Experiencing the same issue and also noted it in the one I opened (#1946).
What is weird is that it works if you initialize the options to a variable before you pass them to any function call.
Description
Thanks for the new queryOptions, it's really useful for prefetching queries in the route loaders. However I have a small issue with queryOptions. The third parameter seems required, even when no parameters is expected.
vs
Reproduction
Last Typescript version (don't know if it matters), an endpoint in the openapi which doesn't need any parameter.
queryOptions should behave the same than other hooks.
Expected result
queryOptions always requires a third parameter (an empty object do the trick however).
Checklist
The text was updated successfully, but these errors were encountered: