Add bindings for `Query` component.

[parkerziegler]

Add bindings for `Query` component.

[kiraarghy]

@parkerziegler

• Agree with the folder structure and namespacing, thanks for explaining!
• I generally prefer pascal case cause snake case brings up memories of my bad python code 🐍. It feels more Reason/OCaml-esque TBH.

[kiraarghy]

I'll take this!

[parkerziegler]

Dope! Assigning you now. I'll probably take Mutation so we can each take a stab at our own approaches and see where we land relative to one another.

[parkerziegler]

FYI @kiraarghy let's copy the folder structure from urql exactly. So for the Query component, let's put it in src/components/UrqlQuery.re and for the hook let's put it in src/hooks/UseQuery.re or something of that sort. Why the weird naming for UrqlQuery? Well, one thing I've thought about is that consumers of reason-urql might have their own Query module somewhere in the tree, with which a Query module might collide. So by namespacing it: http://2ality.com/2017/12/modules-reasonml.html#namespacing-modules, we prevent these potential collisions. In our top level ReasonUrql.re we'll just alias them to their true names, i.e.

/* ReasonUrql.re */
module Query = UrqlQuery

I'd also be curious about using snake case for modules rather than pascal case. I know Wonka uses snake case 🤔 Any feelings or opinions here? What reads to you as more Reason-y?

[parkerziegler]

Cool! Let's stick with pascal case! 🚀 🚫 🐍

[parkerziegler]

Let's not worry about useQuery right now. Until ReasonReact gets support for hooks, I'm leery of trying to do any sort of hacking to support this.