Mikkel

> I definitively agree this is something we need to solve somehow. I'd say the issue primarily lies in the following: > > * The Relay compiler has no concept...

I think that could work. It would have to be nullables all way down to cover our concrete use case, where the nullable fields are on a deeper type. `Js.Nullable.t`...

We use both `reason-apollo-hooks` and `graphql_ppx_re` in production and need both updateQuery and optimisticResponse (The latter is in our fork. Will create a PR after getting our changes updated for...

Just took a look at `ApolloHooksMutation` which wraps `mutate` in `useMemo`. I think that's a mistake for similar reasons as I mention above.

> @mbirkegaard Hey, can you please rebase your branch onto master, so the CI checks run on this PR? Done

Casting like this in `define.ts` ``` resolve: opts.resolve ?? ((v: Event) => v as unknown as Out) ``` makes the argument to resolve `unknown` which makes this typecheck ``` //...

I updated the references to the spec and graphql-js in the description, but I'm a bit confused about whether the behavior I've read into this is actually what the spec...

I'd be happy to add the failing query and seeing about fixing it also. Let me get get the build and tests working first (as per my questions in #205)

There's (very roughly) about 150-ish object types in the schema. For the second question: Do you mean just the union objects themselves or do you mean how many types are...

Can you give any pointers on how to diagnose this issue? I've now encountered it in queries with only a single union. I wanted to try to diagnose it by...