Support @nestjs/graphql@11

[tripss]

Support @nestjs/graphql@11

[TriPSs]

@GP4cK would appreciate that! Thanks for the help!

[GP4cK]

@TriPSs in nest/graphql, between 10.1.6 and 10.1.7, a change was introduced which make the graphql tests not independent.

I asked for some help from the nestjs team but so far, we haven't managed to come up with a solution.

Actually, even today, the tests are not super clean. For example, if you look at the snapshot for the test one read relation:

nestjs-query/packages/query-graphql/__tests__/resolvers/relations/read-relation.resolver.spec.ts

Line 40 in ae98128

it('should use the object type name', () => expectResolverSDL({ one: { relation: { DTO: TestRelationDTO } } }))

The snapshot is:

nestjs-query/packages/query-graphql/__tests__/resolvers/relations/__snapshots__/read-relation.resolver.spec.ts.snap

Lines 995 to 1043 in ae98128

	exports[`ReadRelationsResolver one should use the object type name 1`] = `
	type TestResolverDTO {
	id: ID!
	stringField: String!
	relation: TestRelationDTO!
	}
	type TestRelationDTO {
	id: ID!
	testResolverId: String!
	}
	type TestRelationDTOEdge {
	"""The node containing the TestRelationDTO"""
	node: TestRelationDTO!
	"""Cursor for this node."""
	cursor: ConnectionCursor!
	}
	"""Cursor for paging through collections"""
	scalar ConnectionCursor
	type PageInfo {
	"""true if paging forward and there are more records."""
	hasNextPage: Boolean
	"""true if paging backwards and there are more records."""
	hasPreviousPage: Boolean
	"""The cursor of the first returned record."""
	startCursor: ConnectionCursor
	"""The cursor of the last returned record."""
	endCursor: ConnectionCursor
	}
	type OffsetPageInfo {
	"""true if paging forward and there are more records."""
	hasNextPage: Boolean
	"""true if paging backwards and there are more records."""
	hasPreviousPage: Boolean
	}
	type Query {
	test: TestResolverDTO!
	}
	`;

Which still includes TestRelationDTOEdge, ConnectionCursor although there are not used in the schema.

I think that if we wrap the class definitions in a function, then it will fix this issue. How about I make a first PR without touching the dependencies, just to refactor the tests and the snippets, and then another one to upgrade nestjs/graphql? Do you agree with this approach?