@customResolver over fetches fileds not stored in the database

[Andy2003]

Describe the bug

Given the existing test

graphql/packages/graphql/tests/tck/directives/customResolver.test.ts

Lines 151 to 169 in 7ad1e91

	test("should not over fetch when other fields are manually selected", async () => {
	const query = /* GraphQL */ `
	{
	users {
	firstName
	fullName
	}
	}
	`;
	const result = await translateQuery(neoSchema, query);
	expect(formatCypher(result.cypher)).toMatchInlineSnapshot(`
	"MATCH (this:User)
	RETURN this { .firstName, .fullName } AS this"
	`);
	expect(formatParams(result.params)).toMatchInlineSnapshot(`"{}"`);
	});

And the documentation

Specifying the @customResolver directive on the field definition keeps fullName from being included in any query or mutation fields and hence as a property on the :User node in the database.

The generated Cypher

MATCH (this:User) RETURN this { .firstName, .fullName } AS this

is wrong, since it includes the filed annotated with @customResolver

Expected cypher should be:

MATCH (this:User) RETURN this { .firstName } AS this

[neo4j-team-graphql]

We've been able to confirm this bug using the steps to reproduce that you provided - many thanks @Andy2003! 🙏 We will now prioritise the bug and address it appropriately.