Jason Kuhrt

@devautor thanks! Will take a look tonight

My investigation is below. Some takeaways - what is the purpose of using `gql-gen` exactly? - I don't have much knowledge about `extends` so can't tell you if you've done...

> so did you get the same error as mine with `extend` No, I pasted _exactly_ what I did and saw in my code blocks > Also, I am using...

:) As a workaround for now, if you centralize your schema so as to not need `extend` then it should work currently.

@devautor discovered that the reason `extend` does not currently work: - is lost at this moment: ```ts } else { schema = importSchema(filePath) ``` - https://github.com/prisma/graphql-import/issues/42 - https://github.com/graphql/graphql-js/issues/922 Also, I...

Hey @otrebu, these model types represent what your server will fetch from the backend(s) (DB, microservice, etc). A model type is something that a resolver implementation can return. The missing...

What if a query field resolver fetches it’s scaler data from one backend data source but fetches the relations from another source. A model maps to/specifies what the return value...

we might want to merge this thread into https://github.com/prisma/graphqlgen/issues/181

> is it not what the resolvers on a type, for a specific field are for? If you can, take a look at the generated resolver types: - root field...

@schickling I was about to open a similar issue tonight. Luckily saw this one. > it's more important to be readable and to provide as much context as possible without...