Abhijeet Singh Khangarot
Abhijeet Singh Khangarot
i think updating storybook addons versions will fix this issue
Hi folks, are there any updates on this ?
@nizamani could it be that the `data` field has `new` key, and it could be referenced like this: ``` { "id": {{$body.event.data.new}} } ``` as this is the default object...
@nizamani Sure, I'm using this docker image `hasura/graphql-engine:v2.1.1`. [This](https://gist.github.com/abhi40308/bb098a0ef0122c5a2141c4a6c3418c8e) is the API call that goes for me. Could you please paste the full `Sample Input` and `Configure Request Body` that...
Sure, go ahead
Hi @BLasan , i didn't get, can you please show some screenshot or gif
> Hi @shlomokraus > > Right now you can use only the [mutation options supported directly by apollo-client](https://www.apollographql.com/docs/react/api/apollo-client.html#ApolloClient.mutate). `onCompleted` and `onError` are react-apollo specific. You can have a similar result...
Use this instead : ``` const [mutateMe, { error, loading, data }] = useMutation(MUTANT) if (error) { console.log(`error in mutation ${error}`) } ``` See : https://github.com/trojanowski/react-apollo-hooks/pull/93
Hi folks, is there any updates on this?
Email notifications are not implemented in backend. Without it being in backed, we shouldn't include in the client for now.