graphql-spec | query language and execution engine | GraphQL library

what's the difference between schema and documents in Graphql?

schema is like this:

I'm documenting all my types, fields and parameters in my schema (SDL), including Query and Mutation at the top - but I can't work out how to add a single piece of documentation for the top-level of the whole schema.

I'm not sure if it's the spec or the tooling - Apollo for example allows me to write schema { }, but not to put anything inside it, or documentation before it.

And there are no examples of it in the docs, particularly at https://graphql.github.io/graphql-spec/June2018/#sec-Descriptions, which shows a "well-described" schema without a top-top-level doc string.

Is this something the spec doesn't cover, or just the tooling?

How would you scan schema for missing resolver for queries and non-scalar fields ?

I'm trying to work with a dynamic schema so I need to be able to test this programmatically. I've been browsing graphql tools for few hours to find a way to do this, but I'm getting nowhere...

• checkForResolveTypeResolver - this only apply to interface and union resolveType resolver
• I can't find a way to know when a defaultFieldResolver is applied
• I tried working with custom directives to add @requiredResolver, to help identify those fields, but custom resolver are far from being fully supported:
  • introspection & directives
  • no graphql-js directives handler (can workaround this with graphql-tools tho)

any help is appreciated !

We are migrating our Apollo Graphql Server v1 projects to v2.

We noticed that there is a change in the error response format.

In v2, the errors list in the response is wrapped within an error object.

But, in v1, it is not so. We want to have a a consistent standard and not introduce the wrapping behaviour in v2.

I understand that GraphQL services may provide add additional fields via extensions as per below link. Link: https://graphql.github.io/graphql-spec/June2018/#sec-Errors

I have tested Apollo GraphQL V2 and this is how it is implemented there.

In v1 it is as expected.

In v1,we see error response as below,