Pavel Nikolov

@romshark I completely agree with you. Being able to add this as a middleware would be a better solution. This way only people who need it can add it.

What exactly would you like to achieve and how moving the validation API would help you?

If the query and mutation resolvers are split, it'd be easy to allow only query requests over HTTP `GET` requests - see issue #108

@abourget, does this mean that, for example, if you want to use both a query and a mutation named `Products`, then in your Go code in the schema resolver you...

TBH, although it might sound like a cliche, there is no short path to where we want to go. Having semantic prefixes feels like magic. And requires internal knowledge of...

Not that I am aware of.

@phifty breaking changes are not acceptable at this stage. Versions and tags will be added shortly.

According to the GraphQL specification/documentation [the integers are 32 bit](https://graphql.org/learn/schema/#scalar-types) (AFAIK, this is due to the fact that it is mapped to the integers used by JavaScript in the browsers)....

This is a very interesting problem... How are you going to pass a number greater than 32bit from a browser? This is not possible, right? Even if we change the...

OK, I understand. I'll reopen the issue, then. Sorry fro the misunderstanding and thank you for your explanation. PR would be welcome.