Guido D'Orsi
Guido D'Orsi
We can currently handle this kind of scenarios using the `mutationsEmitter`: ```js import { useContext, useEffect } from "react" import { ClientContext } from "graphql-hooks" import { CREATE_USER_MUTATION } from...
I was thinking about this kind of API: ```js import { useContext, useEffect } from "react" import { useMutationListener } from "graphql-hooks" import { CREATE_USER_MUTATION } from "./somewhere" const LIST_USERS_QUERY...
> The mutation will happen on page 2. But you can't listen to it from page 1 The key is generated taking the variables in account so in that case...
> If we want to update the cache on subscriptions, can it be done in this same way? I've never used them, but until you can hook into some events...
@castarco I've updated the example with the missing parts (I've also realized that I was missing the `createUser` call XD) @nuragic Thanks for the examples, very helpful! It should be...
Ok thanks! > are you actually working on it? Nope
Thanks for handling this! @mahenrique94 Sorry that I didn't answer in time, but your solution seems to be pretty solid :+1:
Managed to create a minimal repro for the issue that was affecting me: https://stackblitz.com/edit/vitejs-vite-tnreze?file=src%2F2_App.tsx,src%2Fmain.tsx,src%2F1_schema.ts&terminal=dev It tourned out that in my case the sync was failing silently when one of the...
Should be fixed with Jazz 0.10.0
We have Svelte and Vue examples now. Moved VanillaJS on https://github.com/garden-co/jazz/issues/2020