Tony Ghita

Hey @jblevins1991, this is already possible. Is there some API you would prefer to be a part of this package to make it easier? This is something I've been considering...

I think this may have to do with the recent changes to the specification not being implemented in this library yet.

Sorry for the delay in picking this issue up. Have you found a solution? Do you know which part of the introspection query is failing?

Okay, if you get the chance to post the error it'd be super helpful! I'll take a shot a reproducing the issue myself.

@sanae10001 that's a good idea. It seems to allow for separation between mutations and the object types. But what happens when you have hundreds of interdependent types in the `objects`...

@sanae10001 I agree that all business logic should not be in resolvers at that scale. I _think_ a large package might be manageable as long as we are aggressive enforcing...

The issue here is that the `flavor` input field is defined as a nullable `String` type, which means `null` or `nil` is a valid value for this field, but is...

Hey, thanks for the question. I'm not sure I completely understand what we are trying to achieve with allowing multiple schema strings... can you expand your question a bit?

Are you looking for a kind of [schema stitching](https://blog.graph.cool/graphql-schema-stitching-explained-schema-delegation-4c6caf468405) functionality? Or is this different?

SemaphoreCI hasn't really handled the `github.com/neelance/graphql-go` -> `github.com/graph-gophers/graphql-go` transition very gracefully :( I'll look into what I can do to straighten it out.