Pavel Nikolov

@marcosgmeli, @sGy1980de I verified and this is a bug indeed. Can be reproduced by: ```go package main import ( "log" "net/http" graphql "github.com/graph-gophers/graphql-go" "github.com/graph-gophers/graphql-go/relay" ) type query struct{} func (*query)...

Actually, after more carefully reading the spec, the library works perfectly fine where in the above example if we don't return the error, the result would be: ```json { "data":...

The only thing that I am not sure about is that some fields return an `Error: ` and others have `(With logged error)`. I wonder what does this mean? Maybe...

@agnivade I'm closing this issue due to inactivity. Feel free to open it if you decide to work on this or in case this feature gets accepted to the official...

@Alien-x and @mjm is this even allowed in the spec?

@mjm thank you for your patience with this PR! I am happy to merge it if you could resolve the conflicts, please. Would you mind doing that?

@mjm That's fine. I'm going to do it. I started cleaning old issues and PRs. I'll either resolve and merge it. Or I'll pick up your unit tests and I'll...

A packer deserialized incoming arguments into type-safe Go struct fields/structs. I'll get back to you shortly.

The schema parsing is done by the lexer and by default it parses a nullable type, however, if it encounters an `!` symbol, then it wraps the type in an...

After carefully reading the issue description I don't believe that this is an issue with the library. It's rather inappropriate use of the optional arguments. The GraphQL spec states [re...