@mcyouks

> Can't just onResult be called with cached result also? It'd solve all problems. 100% agree 👍

> `{fetchPolicy: "network-only"}` (or `"no-cache"`) ([documentation](https://v4.apollo.vuejs.org/api/use-query.html#parameters)) seems to work as a band-aid solution. No doubt, but caching the response offers great UX benefits. Calling `onResult` systematically (including with cached results)...

Hi @jofftiquez 👋 Any update on the timeline ? Thanks

Hello @jofftiquez , thanks for your work. Looking forward to seeing Vue 3 support for this project 😄

Hi all, any update on the Vue 3 migration? 🙂

Thanks for sharing this resource @kfern 🙏

I am using Vite + Vue 3. Did anyone figure out a simple workaround?

Any update on this issue? Has a graphql loader been released to work nicely with Vite2, Vue3, and Vue Apollo? Thanks

Thanks for your reply 🙏 Great enhancement 👌 > Now we have provided > > ``` > const handler = useKBarHandler() > // handler.value.show() > // handler.value.hide() > // handler.value.toggle()...