Gorkem Baris Yesiltas
Gorkem Baris Yesiltas
I am getting the exact same error with `@tanstack/vue-query`, specifically when I'm using the `error` that's returned by `useQuery`. And indeed, changing the name of the `error` variable fixes the...
Hey guys, I can imagine people who are working on this package are very busy and I don't want to be annoying but I think the fact that your tests...
For us, the biggest issue of not being able to have variables with name `error` is fixed. But we still have issues with components where there is a prop called...
Hey, is there an update on this? :)
hey is there any update on this issue?
For what it's worth, I tried diving a bit deeper into this, and I think there are multiple vue instances being initialized in the test environment causing this issue. See...
@maximilianmaihoefner > This seems to work, although I still get warnings like: Yeah, I think it makes sense since we now probably register the plugin multiple times in _some_ places...
I have the same issue. 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...
Update from my side about `useQueries`, looks like [this PR](https://github.com/TanStack/query/pull/6471) from tanstack-query did fix the typing issue :) 🥳
@harryi3t >IIUC this library is not just to help co-locate the queryKey/queryFn but also to auto generate the hierarchical query keys for which there is still no good solution. This...