Fix queryRunnerArgsFactory for updateMany resolver

[ijreilly]

This was updated a few weeks ago and went unnoticed since 1) integration tests were broken + 2) we don't have actionnable updateMany mutations in the product at the moment

It will fix some tests, at least all-people-resolvers.integration-spec.ts for instance

[greptile-apps]

PR Summary

Fixed a critical bug in the UpdateMany resolver's data handling within the QueryRunnerArgsFactory, affecting bulk update operations.

• Modified packages/twenty-server/src/engine/api/graphql/workspace-query-runner/factories/query-runner-args.factory.ts to process a single data object instead of an array for UpdateMany operations
• Fixed incorrect type usage from UpdateOneResolverArgs.data to UpdateManyResolverArgs.data
• Aligned UpdateMany data handling with UpdateOne resolver for consistency
• Impacts integration tests, particularly all-people-resolvers.integration-spec.ts

_{1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Incorrect type cast here - using UpdateOneResolverArgs.data when handling UpdateMany case. This could cause type safety issues.

Suggested change

	data: await this.overrideDataByFieldMetadata(
	(args as UpdateOneResolverArgs).data,
	options,
	(args as UpdateManyResolverArgs).data,
	options,

[ijreilly]

unlike with CreateMany, data is not an array:

export interface CreateManyResolverArgs<
  Data extends Partial<ObjectRecord> = Partial<ObjectRecord>,
> {
  data: Data[];
  upsert?: boolean;
}

...

export interface UpdateManyResolverArgs<
  Data extends Partial<ObjectRecord> = Partial<ObjectRecord>,
  Filter = any,
> {
  filter: Filter;
  data: Data;
}

[ijreilly]

@eliasylonen FYI :)