Custom global fieldResolver called on introspection fields

[southpolesteve]

Ran into this when adding a custom schema wide fieldResolver. This resolver will also get called for introspection fields which was surprising to me. Is this the expected behavior?

[fredericnowak]

I ran into the same issue, when launching the graphiql console.
@southpolesteve did you find a workaround or a way to fallback to the default fieldResolver ?

[southpolesteve]

@growak I ended up copying the default resolver behavior into my custom resolver and checking the type via the info argument to make sure it is my type and not a built in graphql type

[fredericnowak]

@southpolesteve thx

[sibelius]

@southpolesteve can you share your solution?

can we close this?

[IvanGoncharov]

Ran into this when adding a custom schema wide fieldResolver. This resolver will also get called for introspection fields which was surprising to me. Is this the expected behavior?

@southpolesteve @fredericnowak @sibelius It shouldn't work like that since field specific resolvers always take precedence over schema wide fieldResolver, see here:

graphql-js/src/execution/execute.js

Line 693 in ae5b163

const resolveFn = fieldDef.resolve || exeContext.fieldResolver;

and all introspection types have assigned resolvers.

How did you construct your schema?
Did you use new GraphQLSchema(, buildSchema or something else?

Such behavior can occur if you construct your schema using buildClientSchema or similar function that doesn't use built-in introspections types.

[southpolesteve]

Sorry I no longer have access to the code where I solved this problem :/

[IvanGoncharov]

I did some testing and you were right. There are a few introspection fields that don't have resolver attached. So I created #1329 PR which should fix this issue.