Raj Nigam

Why install anywhere when you can run in the cloud? [TODOit As A Service](http://rajington.github.io/TODOit/)

If only you had added it to your "things I should accomplish agenda" like I did.

what fixed it for me was making sure all my jest deps were installed with a `yarn install`

Just to throw in another datapoint, I had the same issue with missing fields in Parse but even the code changes you recommend didn't fix it. _Sometimes_ it worked fine...

could this be the same as (rough code): ```typescript const useFragment = (fragment, id) => useApolloClient().readFragment({ id, fragment }) ``` ?

You could try [`actions-netlify`](https://github.com/rajington/actions-netlify/tree/feature/branch-deploy#usage) which uses the JS client

Although standardizing would be great, might be worth mentioning/re-mentioning: - `graphql-tag`'s [flag](https://github.com/apollographql/graphql-tag#experimental-fragment-variables) - `@graphql-codegen`'s [clientside support](https://www.graphql-code-generator.com/plugins/typescript/typescript-operations) `experimentalFragmentVariables` - `envelop`'s [server approach](https://www.envelop.dev/docs/guides/using-graphql-features-from-the-future#fragment-arguments) - the `graphql-js` PR they [proposed](https://github.com/graphql/graphql-js/pull/3152) as well

sorry, I meant [GraphQL Operations](https://spec.graphql.org/June2018/#sec-Language.Operations) as in the actual `mutation` and `query` (lowercase) calls _to_ the schema

Definitely outdated so not sure if it's relevant, or had it been mentioned now something like useSWR would be included, but [in the v17 docs Apollo is mentioned directly](https://17.reactjs.org/docs/concurrent-mode-suspense.html). I...

> unfortunate pattern of two copies of queries in the codebase this does handle the, likely pretty realistic, use case that the operation changes when migrating. it also lets you...