Fork me on GitHub
#graphql
<
2017-06-27
>
mihaelkonjevic05:06:30

Here’s an alternative with a different philosophy (uses GraphQL language) https://github.com/retro/graphql-builder

bbloom20:06:33

in lacinia is there a reasonable way to differentiate between client errors and server errors? ie query/variables is invalid vs database is down?

hlship20:06:44

The :data key will only be present if the query is valid. Parsing errors, missing required arguments, and so forth, result in an invalid query and just an :errors key in the response.

hlship20:06:03

If you get past that point, there will be a :data key, even if it is nil.

hlship20:06:20

In 0.18.0, exceptions thrown by field resolvers will be captured and converted into error maps.

hlship20:06:48

In 0.19.0 (not yet released), exceptions thrown by field resolvers are not caught at all.

hlship20:06:27

Does that help?