issue with [@types/pg]. it's impossible to pass mixed-type values.

[hakyonglee]

When upgrading from version 8.11.2 to 8.11.3, there was a change in the code as follows.

version 8.11.2

export interface QueryConfig<I extends any[] = any[]> {
    name?: string | undefined;
    text: string;
    values?: I | undefined;
    types?: CustomTypesConfig | undefined;
}

version 8.11.3

export interface QueryConfig<I = any[]> {
    name?: string | undefined;
    text: string;
    values?: QueryConfigValues<I>;
    types?: CustomTypesConfig | undefined;
}
export type QueryConfigValues<T> = T extends Array<infer U> ? (U extends never ? never : T) : never

Due to this, it has become impossible to provide mixed-type values as in pool.query({text, values: [1, 'a', null]}).
Please address this issue.

[typescript-bot]

Thanks for the discussion about "pg", some useful links for everyone:

• npm
• DT
• Related discussions

Pinging the DT module owners: @pspeter3, @HoldYourWaffle.

[codershiba]

Will be fixed by PR #69053

[elielberra]

It seems to me that the PR 69053 didn't solve this issue. I think that the distributive conditional of the QueryConfigValues type is not being correctly handled. I have added a possible solution and a potential new pull request on the typescript playground I am leaving at the end. Please let me know if something was not clear enough. Thanks! https://tsplay.dev/WY1y3W