[object Object] is returned from a binding when resolver throws an error

I’ve noticed that when a query/mutation is executed via a graphql binding an [Object object] error is returned. This behaviour is observed when an error is thrown in resolver as a part of a business logic.

const resolvers = {
  Query: {
    test: async (parent, args, context) => {
      // some random _id that is passed as a query arg 
      const _id = '507f1f77bcf86cd799439011';
      const binding = await context.bindings.organisations.query.organisation({ _id }, '{ _id }', { context: { foo: 'foo' } });
      return 'foo';
    }
  }
};

organisation query throws an Apollo error when organisation is not found by id.

Funny enough the cause is an old version of graphql-tools and the PR for it was already made: https://github.com/graphql-binding/graphql-binding/pull/161

When will it be merged?

[Pajk]

I found a workaround at https://github.com/apollographql/graphql-tools/issues/480#issuecomment-444318754.

For anyone interested:

import { onError } from 'apollo-link-error'
import { createHttpLink } from 'apollo-link-http'

// ...

const errorLink = onError(args => {
	if (args.graphQLErrors && args.graphQLErrors.length === 1) {
		args.response.errors = args.graphQLErrors.concat(new GraphQLError(''))
	}
})

class XXXBinding extends Binding {
	constructor(uri: string) {
		const schema = makeRemoteExecutableSchema({
			schema: fs.readFileSync(schemaPath, 'utf-8'),
			link: errorLink.concat(
				createPersistedQueryLink().concat(createHttpLink({ uri, fetch }))
			),
		})
		super({ schema })
	}
}

[yaacovCR]

Anyways:

https://github.com/apollographql/graphql-tools/pull/1206