teh

@harendra-kumar if it's working for you and @sunwukonga we should include it. Do you want to open a PR?

Thanks! Can you change [this](https://github.com/haskell-graphql/graphql-api/blob/3330f898556d4956d1c785be02cc9c0ef16745f9/scripts/hpc-ratchet#L40) to the value 1364? I believe that will fix the test.

A slightly disgusting hack: We could encode the input object defaults as symbol kinds (aka strings) and then parse them on validation: ```haskell type Query = Object "Query" '[] '[...

Yea, I'm mentioning that option in my summary, it has the downside that you can have only one `(Argument "foo" Bool)` in your entire program. The super correct way would...

Probably not trivial with attoparsec though we could of course count manually: https://github.com/bos/attoparsec/issues/16

Looks good, thank you! To make the test pass can you adjust `COVERAGE_TOLERANCE` like in [this diff](https://github.com/haskell-graphql/graphql-api/pull/186/files#diff-89eb7a8abf17e1052cb2ef2731a0c695)?

Experience from Aeson shows that we want to be very clear about the difference between a missing field and `null`. `Maybe` can communicate both, but in JSON missing and `null`...

@harendra-kumar For the specific error you mention there aren't any easy fixes. We're trying to constrain the type machinery as much as possible where we can but we don't have...

@russmatney I think for now parsing the JSON request yourself is the way to go. I haven't yet managed to convince myself that the `FromJSON` instance in #128 is what...

@theobat PRs are very welcome, *especially* doc PRs! JSON handling is delayed until someone has time to pick it up. My feeling is that the parsing should by type directed...