Prisma Client: wrong type when using spread operator to set default values on query args

[AntonyZ89]

Bug description

I'm using spread operator to set default values on query args of my findMany() function, but when I use it the generated type is incorrect.

How to reproduce

Repository class:

class ComponentRepository {
  /* ... */

  findAll<T extends Prisma.ComponentFindManyArgs>(
    params?: Prisma.SelectSubset<T, Prisma.ComponentFindManyArgs>,
  ) {
    return this.prisma.findMany({
      // default `include`
      include: { componentProp: true, componentStyle: true },
      ...params,
    });
  }

  /* ... */
}

If I pass only params as args of findMany the type of component.componentStyle (see below) is correct.

class ComponentRepository {
  /* ... */

  findAll<T extends Prisma.ComponentFindManyArgs>(
    params?: Prisma.SelectSubset<T, Prisma.ComponentFindManyArgs>,
  ) {
    return this.prisma.findMany(params);
  }

  /* ... */
}

Expected behavior

componentStyle need exists in component.componentStyle.

Prisma information

const componentWithImages = await this.componentRepository.findAll({
  where: {
    overlayId,
    id: {
      notIn: params.map(({ id }) => id),
    },
    componentStyle: {
      some: { key: 'backgroundImage' },
    },
  },
  // override include
  include: { componentStyle: true },
});

for (const component of componentWithImages) {
  /**
    * error TS2339: Property 'componentStyle' does not exist on type '({ componentProp: (GetResult<{ componentId: string; key: string; value: string; variableAssign: string | null; type: ComponentPropType; }, unknown> & {})[]; componentStyle: (GetResult<...> & {})[]; } | {} | { ...; } | undefined) & GetResult<...> & {}'.
    */
  const style = component.componentStyle.find(
    (s) => s.key === 'backgroundImage',
  );

  /* ... */
}

Environment & setup

• OS: WSL 2 Ubuntu 22.04.1 LTS
• Database: PostgreSQL
• Node.js version: v18.14.0

Prisma Version

prisma                  : 4.16.1
@prisma/client          : 4.16.1
Current platform        : debian-openssl-3.0.x
Query Engine (Node-API) : libquery-engine b20ead4d3ab9e78ac112966e242ded703f4a052c (at ../../node_modules/.pnpm/@prisma+engines@4.16.1/node_modules/@prisma/engines/libquery_engine-debian-openssl-3.0.x.so.node)
Migration Engine        : migration-engine-cli b20ead4d3ab9e78ac112966e242ded703f4a052c (at ../../node_modules/.pnpm/@prisma+engines@4.16.1/node_modules/@prisma/engines/migration-engine-debian-openssl-3.0.x)
Format Wasm             : @prisma/prisma-fmt-wasm 4.16.0-66.b20ead4d3ab9e78ac112966e242ded703f4a052c
Default Engines Hash    : b20ead4d3ab9e78ac112966e242ded703f4a052c
Studio                  : 0.484.0

[Jolg42]

I can reproduce on 4.15.0/4.16.1/4.17.0-dev.38(latest internal dev version)

[dkelsen]

This still appears to be an issue with conditional spreads.

// Missing `venue` property in type.

const events = await prisma.event.findMany({
        take: first,
        ...(cursor && {
          skip: 1,
          cursor: {
            id: cursor,
          },
        }),
        include: {
          venue: true,
        },
      }))

[Jolg42]

@dkelsen This is issue is closed, could you open a new issue? We would need more information to reproduce and confirm.