Magnus Hallin

Hmm, I see. So how would you say "use the default value for this column" - would you just omit the argument from the object? Conceptually, omitting an argument optional...

Alright, so one workaround right now would be to break up the input object in the query, like ```graphql mutation ($name: String!) { createEvent(input: { event: { name: $name }...

Hello! I've been preparing support for native code generation, and the source instructions have become a bit outdated. I suggest you start working from the most recent release (https://github.com/mhallin/graphql_ppx/tree/0.2.8) instead....

One option could be to run qemu (http://erouault.blogspot.com/2016/09/running-freebsd-in-travis-ci.html), which could be helpful for https://github.com/mhallin/graphql_ppx/issues/53 as well.

I haven't done any profiling on larger schemas so it's unfortunately possible that there are accidentally quadratic behaviors lurking here and there. Regarding your schema: * How many object types...

Thanks for this. It looks like it basically flips the default of converting `None` into `null` to `undefined` instead. Is this correct?

I'm a bit weary about this since it changes behaviour in a way that might break clients, so it might be better to just bite the bullet and introduce either...

Are there hosted arm64 CI services available, or is anyone familiar with OCaml's cross compilation story here who wants to help out?

What does your schema look like; does it contain a `signUp` mutation with those fields? It's definitely a bug that the error message is an `Option_unwrap_error`, so I'm a bit...

Thanks to #7, this might be solved if you were using either relative or `~` paths. Could you please upgrade to 0.4.0 and try again?