Andrew Pratt
Andrew Pratt
Hi Anders, Right now no, there is no break when recursively generating the query. I think the cleanest approach to adding this feature would be to add a new annotation...
looks great, thanks for the contribution! Could you please resolve the conflicts, @jleibund?
http://facebook.github.io/graphql/June2018/#sec-Errors ``` GraphQL services should not provide any additional entries to the error format since they could conflict with additional entries that may be added in future versions of this...
And please keep all changes in this PR, do not close it to open a new one
#23 relates here
Unfortunately `errorType` is not defined in the GraphQL spec though and I am trying to keep parity with that. It would be best if we could make the Error class...
So, as mentioned in #22 - one of the most popular GraphQL server libraries allows error messages to be formatted any way the user specifies through the `formatError` function (https://github.com/graphql/express-graphql#options)...
@smfaizalkhan this pull request isn't merged so it is not in any release; please see my comment above for a better way of achieving this
Hi @tberman! Currently this feature is not implemented. The reason for this is that I couldn't figure out an intuitive way to do this and since inline fragments were a...
I like the idea of a operation class to distinguish that parameter separately from the fields, it could clean the code up a lot. But I think a good first...