Including meta fields when querying the schema for an object type's fields about graphql-js HOT 3 CLOSED

This is good feedback.

There are a couple reasons meta fields are not returned as part of introspection, the biggest of which is just noise which tools need to work around.

However I think we're open to discussing this further.

from graphql-js.

I also expected that, but I can see how __typename can be considered part of the executor, not part of the underlying schema.

from graphql-js.

Closing this aging issue.

For posterity: it is intentional that the meta-fields (__schema, __typename) are not part of type definitions. We do this to avoid adding repetitive noise and because the fields were in fact never directly defined by the type.

Tools which use the schema that wish to be aware of metafields need to account for this. That's the tradeoff.

from graphql-js.