Joel Jeddeloh

This should be resolved in both #117 and #122 branches. The variables arg is required and there are some convenience functions and Extension modules for making the ergonomics better.

Great. Unless someone wants it first, I'll plan on starting with `useQuery` and following it to the end, sticking as close as possible to `@apollo/client` and get a PR up...

@fakenickels @jfrolich #122 is up for discussion. @jfrolich, I see now I should have been paying attention to the graphql channel on discord! Seriously, this `graphql-ppx` 1.0 is like the...

This seems convenient. I'm going to give it a try on reason-apollo-client as well!

Attempting to parse partial data was one case: https://github.com/jeddeloh/rescript-apollo-client/issues/46 I think there are other reasons to do this, though. Are there tradeoffs besides the cognitive overhead of having to deal...

That does seem like a better solution to a partial data scenario. Here are a few other examples of when parse might raise an exception: - Reading from the cache...

Haha, I think we're just rehashing the exact same discussion we had around promises. I think a function that returns a result should always return a result and you think...

> Well you shouldn't do that haha Regardless, you put a ton of energy into the community, graphql-ppx, and this library. If we can change the ergonomics of the library...

I'm aligned on the GraphQL part at this point, thanks for bearing with me! But if we return to the original issue I referenced about partial data, it was never...

I don't have a ton of clarity at this point how we make things typesafe for `errorPolicy` when set globally, or whether we can simply get around the issue in...