graphql-go

graphql-go copied to clipboard

Error Messaging on "type of kind OBJECT can not be used as input"

3

I encountered this error while defining my schema, but I didn't have any idea how to fix it. Eventually I found the error message in `graphql-go`'s source and found this...

B-Reif

Feature request: Pre-exec

1

Add a configurable preprocesing query ("clasification") during the validation phase of execution. This is utils for the phase of resolver. We think that the solution for this could be similar...

arquio

application/graphql support

1

Is there any support (or plans for it) for this content type for input? e.g. I expected the following request to work from the simple server example in the readme:...

zombor

Pre-parsed queries and/or Query caching

8

Right now when you execute against the schema, it parses the queries each time. We could speed up these executions by either parsing some queries beforehand or caching previously seen...

matthewmueller

Introspection must provide input type for arguments

7

I'm trying to use our [graphql-go](https://github.com/neelance/graphql-go/) based API in combination with [Graphcools GraphQL Playground](https://github.com/graphcool/graphql-playground) and [GraphiQL](https://github.com/graphql/graphiql) and I'm getting the following error in both: `Introspection must provide input type for...

romshark

Moving the schema into its own file allows for syntax highlighting and a cleaner reading experience. A `Makefile` is also included to simplify the execution of `go generate` to transpile...

lamebear

panic occurred: interface conversion: resolvable.Resolvable is nil, not *resolvable.Object

5

hey guys, how do I get past this error and what am I doing wrong? `panic occurred: interface conversion: resolvable.Resolvable is nil, not *resolvable.Object` below I have my schema and...

thewillhuang

Introduces name validation for types, directives, and entry points. The rules are outlined in the GraphQL spec ([1](http://facebook.github.io/graphql/draft/#sec-Schema), [2](http://facebook.github.io/graphql/draft/#sec-Naming-conventions)) and quoted below: > All types within a GraphQL schema must...

tinnywang

Allow multiple schemas and resolvers

4

Hi, I'm writing Go / GraphQL applications and I'm looking to make everything a "module" / "plugin". Is there any plan to allow slice of schemas and resolvers for `MustParseSchema`...

mytototo

### Expected behavior Given the schema ```graphql interface Namer { name: String! } type User implements Namer { id: ID! name(type: NameType = FULL): String! email: String! } enum NameType...

tonyghita