avocadowastaken
avocadowastaken
Hey @githong-kr! I've add tests for this case https://github.com/umidbekk/prettier-plugin-prisma/commit/74452ff1ae631e1768d182005f0f5eb45e9b49bf, but couldn't reproduce the problem. Can you try to format with [`npx prisma format`](https://www.prisma.io/docs/reference/api-reference/command-reference#format), maybe it will provide more info regarding...
Hey @githong-kr, `referentialIntegrity` is still in preview, so I guess that's why it's not fully covered by formatter, I suggest you to leave a comment in https://github.com/prisma/prisma/issues/9380 cc @tomhoule 🙏
As workaround - you can ignore this warnings in app entry: ```javascript if (__DEV__) { // eslint-disable-next-line global-require require("react-native").YellowBox.ignoreWarnings([ "Warning: Failed child context type: Invalid child context", ]); } ```...
It was fixed in [1.0.0-alpha.2](https://github.com/final-form/react-final-form-hooks/releases/tag/v1.0.0-alpha.2), try to install with `next` tag: `react-final-form-hooks@next`. See also #21
It can be achieved with [fetchPolicy](https://www.apollographql.com/docs/react/api/react-apollo.html#graphql-config-options-fetchPolicy) option.
Checking for `mutation` itself is not enough, we have to check for changes of `options` parameters, and this will create unnecessary memoization most of the times. Anyways, React team does...
We also can `useRef` to imitate `this` in class components: ```ts export function useMutation( mutation: DocumentNode, baseOptions?: MutationHookOptions ): MutationFn { const client = useApolloClient(); // Use refs to access...
`useMutation` proxies all options to [`client.mutate`](https://github.com/trojanowski/react-apollo-hooks/blob/master/src/useMutation.ts#L48), it looks like an issue in apollo-client.