Finish bindings for useQuery

[fakenickels]

• fetchMore
• refetch

[hew]

It seems like I can't make a query where I pass through options. Is that the result of the unfinished bindings, or do you think I am just doing something wrong?

[hew]

Regardless, I'll see if I can finish this up.

[fakenickels]

do you mean this param? https://github.com/Astrocoders/reason-apollo-hooks/blob/master/src/Query.re#L42

[hew]

Yeah when I provide ~options, I can't return the (simple, full) tuple. But if I don't pass options, I can.

[hew]

Ah, nevermind. I had (~options) vs (~options, ()). My mistake!

[fakenickels]

oh I see!
maybe there is another way to make this more explicit for users? Point about that in the README?

[hew]

I think what I will do that might be of broader use is write a blog post on common compiler errors in reason that include this one. I think it's less a problem with this library's API design or readme, and more that the optional labeled arguments syntax is 1.) easy to forget, and 2.) isn't really pointed out that well by the compiler.

[fakenickels]

That makes sense!

[fakenickels]

https://github.com/apollographql/react-apollo/tree/master/packages/hooks#a-usequery

[fakenickels]

refetch bound, now just fetchMore missing

[MargaretKrutikova]

I just wanted to rewrite an app from reason-apollo into reason-apollo-hooks and need fetchMore, so I would be glad to help write bindings for it. Is someone already working on it?

I was also thinking about including network status in the same change since it seems useful to distinguish between just loading status and fetching more, NetworkStatus type from apollo-client package.

[fakenickels]

None of us are working on it, your help here would be much appreciated!

[MargaretKrutikova]

Great! I will start working on it.