This is the current definition of the QuerySqlToken

And the current definition of the sql.unsafe:

As a result, queries that are constructed via the sql.unsafe tags return results of any / any[], etc. A few releases ago we were getting readonly any[] types which did not trigger the @typescript-eslint/no-unsafe-assignment rule

Desired Behavior

I would prefer if slonik could return results of unknown / unknown[] types for such queries. This would still force the developer to do the runtime type validation (we use typebox instead of zod) but with the additional type-checking upsides

Implementation

It would probably be enough to do the following:

// sql-tag/src/types.ts
T extends StandardSchemaV1 = StandardSchemaV1<unknown, unknown> // instead of T extends StandardSchemaV1 = StandardSchemaV1<any, any>

// sql-tag/src/factories/createSqlTag.ts
parser: z.unknown()  // instead of parser: z.any()